Date: Mon, 8 Nov 1999 13:04:29 +0200 From: Valentin Nechayev <netch@lucky.net> To: Eivind Eklund <eivind@FreeBSD.ORG> Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/libexec/uucpd uucpd.c Message-ID: <19991108130429.A45693@lucky.net> In-Reply-To: <19991107142522.L72085@bitbox.follo.net>; from Eivind Eklund on Sun, Nov 07, 1999 at 02:25:22PM %2B0100 References: <199911062058.MAA72645@freefall.freebsd.org> <382573E1.66E8AF35@newsguy.com> <19991107142522.L72085@bitbox.follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Eivind Eklund! Sun, Nov 07, 1999 at 14:25:22, eivind wrote about "Re: cvs commit: src/libexec/uucpd uucpd.c" in cvs-commiters@, cvs-all@: > > Just for the record, this is considered a really bad thing, because > > one common error is typing the password when the username is being > > expected. > > > > Of course, in an automated environment without user intervention, > > that's probably not relevant. But I'd rather just remark on it > > anyway. :-) > > I wouldn't expect anybody to do UUCP manually. The standard practise is to use UUCP on network access server with some pass (rlogin, etc.) to real uucp server. When script fails in something (incorrect waitings, modem failures, cable failures...), it can send password when server expects login, and vice versa. > The servers I originally did this change for has about a thousand > customers using UUCP-over-TCP, using various systems. I've not seen > any passwords end up in the log; however, it has made it possible to > contact users with problems, and to see why we continiously got logged > password failures (answer: Some broken client sending 'quit' on the > username prompt before disconnecting). You have quite good phone lines and customers have good cables and ports. In some places it is not standard, but hope ;( > I don't have any religious feeling about this change, and I'm willing > to back it out and keep it as a local change again (the way it has > been for a year or so). I just thought it would be considered an > improvement for other users, too. Possibly it should be turned off by default and turned on in config. -- NVA 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?19991108130429.A45693>