9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Vadim Antonov avg@postman.ncube.com
Subject: secure login without digital pathways box
Date: Thu, 17 Aug 1995 23:42:11 -0400	[thread overview]
Message-ID: <19950818034211.qt3c8Qmw3gkMblBs6jN9YYPJ7BEz4QfNRLCA2vTrGXY@z> (raw)

-----BEGIN PGP SIGNED MESSAGE-----

Look for "fcrypt" at European FTP servers (ftp.funet.fi?)
The source for DES was available everywhere outside US
for at least a decade.

As for reducing security -- when a corporation has all
really valuable data stored on Unix machines it makes
very little sense to protect toys zealously.  Also,
challenge-response schemes do not protect against active
snoopers (you can always "steal" an already authenticated
TCP or UDP session) and so are of very little value as
protection against Ethernet snoopers (to steal packets
you already have to have access to a machine on the Ethernet,
ok?)

This means that you still need a solid firewall, no matter
if you use one-time passwords or not.  Over long-distance
links the one-time-password schemes are vulnerable to
host-route attacks (a man-in-the-middle scheme) or compromised
source hosts (i.e. the securenet thingie can't protect you
if you're logging from a host with doctored telnet).

The real answer to the network security is the encryption of
all data and using key exchange schemes resistant to the
man-in-the middle attacks.  And, also, *never* log in from
a machine you don't trust.  Better carry your own laptoy,
as security of the machine is as good as its physical
security.  There's no magic bullet.

So, the options i added are designed for use inside protected
LANs, where excessive level of paranoya only makes people
irritated (and by doing so _compromises_ security, as then
the users will tend to circumvent authentication so rendering
it useless). 


- --vadim

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMDTfQUDODjim2XUVAQEf1gP8DIh6ORzpLA4kslZ90Vk5igudSF5ZZpZP
Kj60qTxNkztRk9X/qEKISPXjfe/Ifmmm5vPlBGPT42gcMvDKWcOrizrt9cTBsTBU
apGzLyUT9AsuMmva4hfd0xyY3QHb/Aj84aRrGYFHtKLlbylpcEjoHtfncqie+R5L
fVA1OYUKk+E=
=bOcB
-----END PGP SIGNATURE-----






             reply	other threads:[~1995-08-18  3:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-08-18  3:42 Vadim [this message]
1995-08-18 11:26 forsyth
1995-08-26  3:49 Boyd
1995-08-26  4:34 Boyd

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=19950818034211.qt3c8Qmw3gkMblBs6jN9YYPJ7BEz4QfNRLCA2vTrGXY@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).