Date: Tue, 27 Oct 1998 16:12:57 -0500 From: josh@ican.net To: current@FreeBSD.ORG Cc: josh@ican.net Subject: Secure RPC/NIS/NIS+ Message-ID: <19981027161257.40034@ican.net>
next in thread | raw e-mail | index | archive | help
A number of questions: 1. Long, long ago (May) there was talk about work being done on getting NIS+ support into -current, possibly by the time 3.0-release rolls about. That time is obviously past, and I was just wondering as to the status of this. 2. I've been poking about trying to find some reasonably useful information on Secure RPC. From what I've been able to tell, all Secure RPC buys you is the ability for one machine to (securely) identify itself to the server, but doesnt actually do any end-to-end encryption of the data stream. Does this mean, were NIS hacked to use Secure RPC, that the encrypted passwords (stored on the master) would still be transmitted on the wire unencrypted (as it were)? Having just set up a small NIS domain, I was struck with the thought that the use of ssh to improve security is somewhat obviated if peoples (albeit encrypted) passwords are flying about in the clear. Would Secure RPC solve this problem? (My guess is no, but it wouldnt hurt to have this confirmed) 3. Long, long, longer ago (last June), Bill Paul made mention of having NIS use Secure RPC. Has anything been done in this direction? thanks josh -- Josh Tiefenbach - Member - ACC Corps of Internet Engineers - josh@ican.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981027161257.40034>