My only real observation is that with Protocol using (2) by default, my
logins to RELENG_4 boxes using RSA key authentication are broken. If I
stick a Protocol 1 in, it works fine, but it took me a bit to figure out
what was going on, and given that scp doesn't support -1, was a bit of a
pain. I haven't tried using OpenSSH 2.9 with Kerberos as yet, but that
would be something to test. Let me know if you need access to a
KerberosIV realm to test with.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
On Sun, 29 Jul 2001, Brian Fundakowski Feldman wrote:
> I need to know, if OpenSSH is ever going to get MFC'ed, are there any people
> currently running OpenSSH 2.9 from -CURRENT's base and getting major
> problems with it? Or even minor ones that actually make things more
> difficult? I want to have no real outstanding issues, except simple ones
> like Protocol being set to 2,1 by default (which is a reasonable default
> nowadays), before I MFC OpenSSH, because I really don't want to leave anyone
> screwed over in the process.
> So let me know, ASAP, what problems you all are having with OpenSSH in
> -CURRENT, specifically in the FreeBSD-specific parts. I'm also not certain
> of KRB4 and KRB5 auth still both work properly, and need that verified.
> Thanks, everybody.
> Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
> [EMAIL PROTECTED] `------------------------------'
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message