From: Steve Kotsopoulos steve@stealth.ecf.toronto.edu
Subject: More on CPU/Auth server
Date: Sat, 13 Apr 1996 18:10:37 -0400 [thread overview]
Message-ID: <19960413221037.9HOt1lMmydIBUzSvQJPnywJS_z0tHK9dYqic5T0zdHw@z> (raw)
[sorry if you see this twice, I got a bounce from my first posting]
Thomas Riemer <triemer@babbitt.BErnstein.COM> wrote:
>I'm booting a PC 486 with a standalone filesystem on hd1fs as a CPU/auth
>server.
Note that this setup may not be safe unless you've disabled logins as none.
Otherwise, someone could telnet into your auth server as none,
run 'disk/kfscmd allow', and then change anything they want.
I have tried this on my standalone terminal, though I haven't
tested it with a cpu kernel to see if it behaves differently.
next reply other threads:[~1996-04-13 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-13 22:10 Steve [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-04-07 1:53 Thomas
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=19960413221037.9HOt1lMmydIBUzSvQJPnywJS_z0tHK9dYqic5T0zdHw@z \
--to=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).