Re: harden-clients idea

2002-10-09 Thread Richard
On Wed, 9 Oct 2002, Jean-Francois Dive wrote: > i reckon that the real point is: if your users have access to the network > from their account with whatever tools or have access to an editor and gcc, > all of your efforts are gone: just need to use your own copy of > whatever_tool_they_like. If

Re: harden-clients idea

2002-10-09 Thread Richard
On Wed, 9 Oct 2002, Jean-Francois Dive wrote: > i reckon that the real point is: if your users have access to the network > from their account with whatever tools or have access to an editor and gcc, > all of your efforts are gone: just need to use your own copy of >whatever_tool_they_like. If

Re: harden-clients idea

2002-10-08 Thread Jean-Francois Dive
i reckon that the real point is: if your users have access to the network from their account with whatever tools or have access to an editor and gcc, all of your efforts are gone: just need to use your own copy of whatever_tool_they_like. If you want to avoid them to go some places, simply use th

Re: harden-clients idea

2002-10-08 Thread Jean-Francois Dive
i reckon that the real point is: if your users have access to the network from their account with whatever tools or have access to an editor and gcc, all of your efforts are gone: just need to use your own copy of whatever_tool_they_like. If you want to avoid them to go some places, simply use t

Re: harden-clients idea

2002-10-08 Thread martin f krafft
also sprach Peter Cordes <[EMAIL PROTECTED]> [2002.10.08.2008 +0200]: > It uses the telnet protocol, not just a raw TCP connection, so netcat is > inadequate. netcat can negotiate telnet connections with the -t option. unless you are using very ancient terminal types, netcat is a complete substitu

Re: harden-clients idea

2002-10-08 Thread Peter Cordes
On Tue, Oct 08, 2002 at 12:47:32PM +0200, Kjetil Kjernsmo wrote: > Hi folks! > > I just had an idea the other, er..., night, that still seemed smart when > I woke up, so I figured I'll post it here in case it is... :-) > > The problem with e.g. telnet isn't really that it shouldn't be used for

Re: harden-clients idea

2002-10-08 Thread martin f krafft
also sprach Peter Cordes <[EMAIL PROTECTED]> [2002.10.08.2008 +0200]: > It uses the telnet protocol, not just a raw TCP connection, so netcat is > inadequate. netcat can negotiate telnet connections with the -t option. unless you are using very ancient terminal types, netcat is a complete substit

Re: harden-clients idea

2002-10-08 Thread Peter Cordes
On Tue, Oct 08, 2002 at 12:47:32PM +0200, Kjetil Kjernsmo wrote: > Hi folks! > > I just had an idea the other, er..., night, that still seemed smart when > I woke up, so I figured I'll post it here in case it is... :-) > > The problem with e.g. telnet isn't really that it shouldn't be used for

Re: harden-clients idea

2002-10-08 Thread martin f krafft
please don't CC me on lists that I read! also sprach Kjetil Kjernsmo <[EMAIL PROTECTED]> [2002.10.08.1402 +0200]: > Oh, wasn't that the point with the harden-clients package? If you > attempt to install a Bad[tm] client, you will be told, because it > conflicts with harden-clients? Oh, now I un

Re: harden-clients idea

2002-10-08 Thread Alvin Oga
hi ya if the machines are hardened and so are the network.. if you attempt to do something like telnet,ftp,ppp,pop3s,dhcp... it just wotn connect/work ... - firewall will drop those services becauses its "against policy" if the admin is NOT notified/emailed/paged .. than the sy

Re: harden-clients idea

2002-10-08 Thread Kjetil Kjernsmo
On Tuesday 08 October 2002 13:57, martin f krafft wrote: > Use netcat for that. [*hm, man netcat*] Yeah, OK, thanks, I didn't know about that. > > That way, people with correct privileges could still use telnet for > > sensible things, yet the admin would be warned if they did > > something very

Re: harden-clients idea

2002-10-08 Thread martin f krafft
also sprach Kjetil Kjernsmo <[EMAIL PROTECTED]> [2002.10.08.1247 +0200]: > The problem with e.g. telnet isn't really that it shouldn't be used for > anything, but that it shouldn't be used by somebody. It is quite OK to > use to check what the webserver responds to a particular request, for > ex

Re: harden-clients idea

2002-10-08 Thread martin f krafft
please don't CC me on lists that I read! also sprach Kjetil Kjernsmo <[EMAIL PROTECTED]> [2002.10.08.1402 +0200]: > Oh, wasn't that the point with the harden-clients package? If you > attempt to install a Bad[tm] client, you will be told, because it > conflicts with harden-clients? Oh, now I u

harden-clients idea

2002-10-08 Thread Kjetil Kjernsmo
Hi folks! I just had an idea the other, er..., night, that still seemed smart when I woke up, so I figured I'll post it here in case it is... :-) The problem with e.g. telnet isn't really that it shouldn't be used for anything, but that it shouldn't be used by somebody. It is quite OK to use t

Re: harden-clients idea

2002-10-08 Thread Alvin Oga
hi ya if the machines are hardened and so are the network.. if you attempt to do something like telnet,ftp,ppp,pop3s,dhcp... it just wotn connect/work ... - firewall will drop those services becauses its "against policy" if the admin is NOT notified/emailed/paged .. than the s

Re: harden-clients idea

2002-10-08 Thread Kjetil Kjernsmo
On Tuesday 08 October 2002 13:57, martin f krafft wrote: > Use netcat for that. [*hm, man netcat*] Yeah, OK, thanks, I didn't know about that. > > That way, people with correct privileges could still use telnet for > > sensible things, yet the admin would be warned if they did > > something ver

Re: harden-clients idea

2002-10-08 Thread martin f krafft
also sprach Kjetil Kjernsmo <[EMAIL PROTECTED]> [2002.10.08.1247 +0200]: > The problem with e.g. telnet isn't really that it shouldn't be used for > anything, but that it shouldn't be used by somebody. It is quite OK to > use to check what the webserver responds to a particular request, for > e

harden-clients idea

2002-10-08 Thread Kjetil Kjernsmo
Hi folks! I just had an idea the other, er..., night, that still seemed smart when I woke up, so I figured I'll post it here in case it is... :-) The problem with e.g. telnet isn't really that it shouldn't be used for anything, but that it shouldn't be used by somebody. It is quite OK to use