Re: root fs/crypted

I see it as more than this. I see it as ensuring that the data on the disk does not get accessed by anyone never intended to see it. (physically, of course). I guess this would mostly be cool for thwarting things like police raids, servers vulnerable in remote locations (e.g. colocation, etc). My

RE: root fs/crypted

there is already a HowTo on how to create an encrypted loop-back "file system". it doesn't encrypt the whole disk, but it could certainly hold anything worth having encrypted. don't get me wrong, i fully understand the reasons behind putting the entire system behind a good pass-phrase. with the w

Re: root fs/crypted

I like this. Would it be difficult to modify Debian, so that upon install, it creates an encrypted root volume and starts things off the right way? -Original Message- From: clemens <[EMAIL PROTECTED]> To: debian-security@lists.debian.org Date: Tuesday, May 29, 2001 6:04 PM Subject: root f

root fs/crypted

SAWFASP^* as laws around the globe are forged to weak personal privacy, police knocking on one's door, because of portscanning a previously hacked website, and - i don't have to tell those of you, which are reading slashdot - as pretty strange things start to happend worldwide, i'm getting somew

RE: root fs/crypted

there is already a HowTo on how to create an encrypted loop-back "file system". it doesn't encrypt the whole disk, but it could certainly hold anything worth having encrypted. don't get me wrong, i fully understand the reasons behind putting the entire system behind a good pass-phrase. with the

Re: root fs/crypted

I like this. Would it be difficult to modify Debian, so that upon install, it creates an encrypted root volume and starts things off the right way? -Original Message- From: clemens <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Tuesday, May 29, 2001 6:04 PM Subject: r

Re: apt and security

actually I thought some sort of log for dpkg/apt would be good, just to keep a record of when something was installed or upgraded. so you know what changed. On Tue, May 29, 2001 at 09:36:37AM -0500, Matthew H. Ray wrote: > I've got tripwire keeping an eye on my filesystems so I'm notified whenever

root fs/crypted

SAWFASP^* as laws around the globe are forged to weak personal privacy, police knocking on one's door, because of portscanning a previously hacked website, and - i don't have to tell those of you, which are reading slashdot - as pretty strange things start to happend worldwide, i'm getting some

Re: apt and security

actually I thought some sort of log for dpkg/apt would be good, just to keep a record of when something was installed or upgraded. so you know what changed. On Tue, May 29, 2001 at 09:36:37AM -0500, Matthew H. Ray wrote: > I've got tripwire keeping an eye on my filesystems so I'm notified wheneve

Re: other mysterious port things

Cesar writes: Hi ! I'm a disquette with this utilities clean. #mount /dev/fd0 /floppy #cd /floppy #./netstat -antp Don't forget to mount "-ro" or write protect the floppy. :-) On linux, AFASIK, "netstat" relies on /dev/net and friends not to lie to it. This is a poor assumpti

Re: Security in general

On Tue, May 29, 2001 at 10:50:07AM +0200, kjfsgjks ksjgkfhfd wrote: > Hi, kjfsgjks: You probably have a real name. Why not use it? > I have a question which has been bothering me all along, with windows / > linux / *bsd / etc. In this case, it's about Debian so I thought I'd post my > question

Re: other mysterious port things

Sorry I "have" :)) Cesar wrote: > > Hi ! > > I have a disquette with this utilities clean. > #mount /dev/fd0 /floppy > #cd /floppy > #./netstat -antp > > Regards > César. >

Re: other mysterious port things

On Tue, 29 May 2001, Ken Seefried wrote: > Tim Haynes writes: > > > > Why do people persist in using nmap at test phase? Sure, if you've > > been cracked, scan yourself if you want, but if you're looking to see `what > > do I have open?' then nmap is the *last* tool I'd use. > > > > Go back t

Re: other mysterious port things

Hi ! I'm a disquette with this utilities clean. #mount /dev/fd0 /floppy #cd /floppy #./netstat -antp Regards César. Ken Seefried wrote: > > Tim Haynes writes: > > > > Why do people persist in using nmap at test phase? Sure, if you've > > been cracked, scan yourself if you want, bu

Re: other mysterious port things

Cesar writes: > > Hi ! > > I'm a disquette with this utilities clean. > #mount /dev/fd0 /floppy > #cd /floppy > #./netstat -antp > Don't forget to mount "-ro" or write protect the floppy. :-) On linux, AFASIK, "netstat" relies on /dev/net and friends not to lie to it. This is a

Re: Security in general

On Tue, May 29, 2001 at 10:50:07AM +0200, kjfsgjks ksjgkfhfd wrote: > Hi, kjfsgjks: You probably have a real name. Why not use it? > I have a question which has been bothering me all along, with windows / > linux / *bsd / etc. In this case, it's about Debian so I thought I'd post my > questio

Re: other mysterious port things

Sorry I "have" :)) Cesar wrote: > > Hi ! > > I have a disquette with this utilities clean. > #mount /dev/fd0 /floppy > #cd /floppy > #./netstat -antp > > Regards > César. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL

Re: other mysterious port things

On Tue, 29 May 2001, Ken Seefried wrote: > Tim Haynes writes: > > > > Why do people persist in using nmap at test phase? Sure, if you've > > been cracked, scan yourself if you want, but if you're looking to see `what > > do I have open?' then nmap is the *last* tool I'd use. > > > > Go back

Re: other mysterious port things

Hi ! I'm a disquette with this utilities clean. #mount /dev/fd0 /floppy #cd /floppy #./netstat -antp Regards César. Ken Seefried wrote: > > Tim Haynes writes: > > > > Why do people persist in using nmap at test phase? Sure, if you've > > been cracked, scan yourself if you want, b

apt and security

I've got tripwire keeping an eye on my filesystems so I'm notified whenever a change is made. I recently added a couple of packages via apt, and I noticed a number of files were modified that I hadn't expected changed. I don't recall the names of the packages I upgraded (there were a bunch), but

Re: other mysterious port things

Tim Haynes writes: Why do people persist in using nmap at test phase? Sure, if you've been cracked, scan yourself if you want, but if you're looking to see `what do I have open?' then nmap is the *last* tool I'd use. Go back to sudo netstat -plan | grep LIST Well...that would be i

apt and security

I've got tripwire keeping an eye on my filesystems so I'm notified whenever a change is made. I recently added a couple of packages via apt, and I noticed a number of files were modified that I hadn't expected changed. I don't recall the names of the packages I upgraded (there were a bunch), but

Re: other mysterious port things

On Tue, May 29, 2001 at 12:07:47PM +0100, Tim Haynes wrote: > sudo netstat -plan | grep LIST just a small note: if your LC enviroment variables are set to other language, you may need to change LIST for other word. (in pt_BR is OUÇA) -- Pedro Zorzenon Neto

Re: other mysterious port things

Tim Haynes writes: > > Why do people persist in using nmap at test phase? Sure, if you've > been cracked, scan yourself if you want, but if you're looking to see `what > do I have open?' then nmap is the *last* tool I'd use. > > Go back to > sudo netstat -plan | grep LIST Well...tha

Re: other mysterious port things

Jogi Hofmueller <[EMAIL PROTECTED]> writes: > lately i was running nmap to check my office machine. to my surprise i > found an open port 'cadsi-lm' (1387). running nmap again the port was not > there anymore. on future runs i found my machine listening on different > registered non-privileged por

other mysterious port things

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi! lately i was running nmap to check my office machine. to my surprise i found an open port 'cadsi-lm' (1387). running nmap again the port was not there anymore. on future runs i found my machine listening on different registered non-privileged port

Re: other mysterious port things

On Tue, May 29, 2001 at 12:07:47PM +0100, Tim Haynes wrote: > sudo netstat -plan | grep LIST just a small note: if your LC enviroment variables are set to other language, you may need to change LIST for other word. (in pt_BR is OUÇA) -- Pedro Zorzenon Neto

Security in general

Hi, I have a question which has been bothering me all along, with windows / linux / *bsd / etc. In this case, it's about Debian so I thought I'd post my question here. Right now I have a linux-box (Debian 2.2r2) doing my masquerading/firewalling. It has a dynamic ip (and changes quite often, l

Re: other mysterious port things

Jogi Hofmueller <[EMAIL PROTECTED]> writes: > lately i was running nmap to check my office machine. to my surprise i > found an open port 'cadsi-lm' (1387). running nmap again the port was not > there anymore. on future runs i found my machine listening on different > registered non-privileged po

other mysterious port things

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi! lately i was running nmap to check my office machine. to my surprise i found an open port 'cadsi-lm' (1387). running nmap again the port was not there anymore. on future runs i found my machine listening on different registered non-privileged por

Re: hi, any help ? about an evil mysterious crazy Open tcp port ?

> how, can i see the tcp port 4350 that states to be opened useing nmap There is _the_ official document of registered ports at http://www.iana.org/assignments/port-numbers and it claims 4350 is "Net Device" - what ever that means. The entry is created by microsoft so we may assume it is some wi

Security in general

Hi, I have a question which has been bothering me all along, with windows / linux / *bsd / etc. In this case, it's about Debian so I thought I'd post my question here. Right now I have a linux-box (Debian 2.2r2) doing my masquerading/firewalling. It has a dynamic ip (and changes quite often, l