On 5 Jul, John Foster wrote:
On Fri, 4 Jul 1997 [EMAIL PROTECTED] wrote:
#!/bin/sh
cat __EOF__
No telnet login allowed.
** Insert the motd here **
__EOF__
sleep 5
exit 0
And if the remote user managed to interrupt it would they get
/bin/sh?, with EUID 0?
And what if the
On Sat, Jul 05, 1997 at 07:44:02AM +1000, John Foster wrote:
On Fri, 4 Jul 1997 [EMAIL PROTECTED] wrote:
#!/bin/sh
cat __EOF__
No telnet login allowed.
** Insert the motd here **
__EOF__
sleep 5
exit 0
And if the remote user managed to interrupt it would they get
hello,
John Foster wrote:
We use the following strategy:
1) Generate a list of passwords with pwgen
could you describe this utility?
2) On a SP2 supercomputer, try to crack them (after feeding them
through crypt).
do you use a wordlist and if so, how big?
3) Those who can't be
-BEGIN PGP SIGNED MESSAGE-
On Thu, 3 Jul 1997, Pavel Galynin wrote:
attempts to telnet from the one source, but as we've disabled shell
access for dial-in clients it'll just give them motd if they do get in
that way!
i'm not at all knowledgeable in linux, but chsh changes a default
hello,
Nils Rennebarth wrote:
-BEGIN PGP SIGNED MESSAGE-
On Thu, 3 Jul 1997, Pavel Galynin wrote:
attempts to telnet from the one source, but as we've disabled shell
access for dial-in clients it'll just give them motd if they do get in
that way!
i'm not at all
On 4 Jul, Nils Rennebarth wrote:
-BEGIN PGP SIGNED MESSAGE-
On Thu, 3 Jul 1997, Pavel Galynin wrote:
attempts to telnet from the one source, but as we've disabled shell
access for dial-in clients it'll just give them motd if they do get in
that way!
i'm not at all knowledgeable in
On Fri, 4 Jul 1997 [EMAIL PROTECTED] wrote:
#!/bin/sh
cat __EOF__
No telnet login allowed.
** Insert the motd here **
__EOF__
sleep 5
exit 0
And if the remote user managed to interrupt it would they get
/bin/sh?, with EUID 0?
And what if the sleep call was suspended?
I don't
As you can see, this message is very offtopic, but still somewhat Debian
related.
I am curious how folks who use Debian in a production environment deal
with allocating passwords.
Do you use the pwgen package and let users worry about it from there, or
do you let them choose within the confines
We use the following strategy:
1) Generate a list of passwords with pwgen
2) On a SP2 supercomputer, try to crack them (after feeding them
through crypt).
3) Those who can't be cracked go into a safe, to be allocated when
users sign up.
The company I work for was very badly hacked (rm -fR *),
9 matches
Mail list logo
