| Title: | -={ H A C K E R S }=- |
| Notice: | Write locked - see NOTED::HACKERS |
| Moderator: | DIEHRD::MORRIS |
| Created: | Thu Feb 20 1986 |
| Last Modified: | Mon Aug 03 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 680 |
| Total number of notes: | 5456 |
I'm looking for some ideas about uniquely identifying that a DECnet
network node is really the node it claims to be.
This is for a new product with a fairly pressing need for security
of this kind.
I'm aware of the possibility of using the processor id, but how
do I cope with �VAXes?
Nigel.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 232.1 | Another notesfile ... | LATOUR::RASPUZZI | Michael Raspuzzi | Tue Apr 15 1986 11:09 | 5 |
Perhaps you should pose this question in the DECnet-VAX notes file.
It is located on BULOVA::DECNETVAX. Press KP7 to select this
conference.
Mike
| |||||
| 232.2 | Sorry... | TLE::BRETT | Tue Apr 15 1986 22:03 | 11 | |
You can't, without exchanging some secret info on a secure link.
The ONLY way is to get a trusted party to carry some secret info.
between the two nodes (eg: a password, encryption key, or whatever).
This is a standard problem in cryptology, and the above result
is fairly obvious. See, for example, recent conversations on
net.crypt.
/Bevin
| |||||