Re: usermod: lock/unlock local password

2013-02-15 Thread Antoine Jacoutot
On Mon, Feb 11, 2013 at 10:11:25PM +0100, André Stöbe wrote: > Antoine Jacoutot wrote: > > This diff adds 2 new options to usermod(8): > > -U to unlock a user's password > > -Z to lock a user's password > > Today I was working with these two switches and really got confused. > I've tested the foll

Re: mg(1): don't handroll TAILQ_REMOVE

2013-02-15 Thread Florian Obser
On Fri, Feb 15, 2013 at 02:07:31PM +, Florian Obser wrote: > While the handrolled version works in this case it thrashes the TAILQ > and sets a bad example. > OK? irgs, throw away undo history of the killed buffer, not current buffer. sorry about that. diff --git a/buffer.c b/buffer.c index 0

mg(1): don't handroll TAILQ_REMOVE

2013-02-15 Thread Florian Obser
While the handrolled version works in this case it thrashes the TAILQ and sets a bad example. OK? diff --git a/buffer.c b/buffer.c index 0b590eb..440d9f0 100644 --- a/buffer.c +++ b/buffer.c @@ -153,7 +153,7 @@ killbuffer(struct buffer *bp) struct buffer *bp2; struct mgwin *wp;

Re: Security and ignorance from the major ISPs

2013-02-15 Thread Michael D. Wood
You will always see constant scanning, its inevitable. All those automated scanners out there now its going to happen. Depending on how you have your firewall setup it really depends on what services you have running behind that firewall. Once you open up that layer to be exposed, another at

Re: install(1) confusing error message

2013-02-15 Thread Giovanni Bechis
On 02/14/13 21:38, Miod Vallat wrote: > This is what happens when install(1) is used to install files on a > read-only filesystem: > > # mount -u -o ro /usr > # cd /usr/src > # make build > cd /usr/src/share/mk && exec make install > install -c -o root -g bin -m 444 bsd.README bsd.dep.mk bsd.lib.

Re: Security and ignorance from the major ISPs

2013-02-15 Thread Stuart Henderson
On 2013/02/14 19:28, Geoff Steckel wrote: > outgoing connections? from secure systems, allow all is > probably OK - though blocking packets to useless > "privileged" ports is probably a good idea. people don't block outgoing connections enough. once you've worked out which outbound connections ac

Re: install(1) confusing error message

2013-02-15 Thread Peter Hessler
better error messages are far better. OK phessler@ On 2013 Feb 14 (Thu) at 20:38:02 + (+), Miod Vallat wrote: :This is what happens when install(1) is used to install files on a :read-only filesystem: : :# mount -u -o ro /usr :# cd /usr/src :# make build :cd /usr/src/share/mk && exec mak