openssh unix dev - Jan 2000 - OpenSSH protocol 1.6 proposal

On Sat, 1 Jan 2000, Brian Fundakowski Feldman wrote:
> 	http://www.FreeBSD.org/~green/openssh.SHA-1.patch
> MD5 (public_html/openssh.SHA-1.patch) = e21a896f59474a31ab3b9103acf44c35
> 
> P.S.:	I realize other people may have proposed something very similar.
> 	Indeed, markus's proposal may be something like this.  However,
> 	since it's impossible to work with anyone who is Theo, or
> 	"under" Theo, it's unrealistic to work with that.  Hence the
> 	reason we need to make a code fork of OpenSSH as soon as
> 	convenient.
i'm sorry you feel this way. so far, the OpenBSD OpenSSH developers and
the Linux/Solaris/etc. OpenSSH developers led by Damien Miller have been
getting along just fine. we hereby cordially invite you to join the party!

	http://violet.ibs.com.au/openssh/list.html

best wishes for the new year.

-d.

---
http://www.monkey.org/~dugsong/

On Sat, 1 Jan 2000, Dug Song wrote:
> On Sat, 1 Jan 2000, Brian Fundakowski Feldman wrote:
> 
> > 	http://www.FreeBSD.org/~green/openssh.SHA-1.patch
> > MD5 (public_html/openssh.SHA-1.patch) =
e21a896f59474a31ab3b9103acf44c35
> > 
> > P.S.:	I realize other people may have proposed something very similar.
> > 	Indeed, markus's proposal may be something like this.  However,
> > 	since it's impossible to work with anyone who is Theo, or
> > 	"under" Theo, it's unrealistic to work with that. 
Hence the
> > 	reason we need to make a code fork of OpenSSH as soon as
> > 	convenient.
> 
> i'm sorry you feel this way. so far, the OpenBSD OpenSSH developers and
> the Linux/Solaris/etc. OpenSSH developers led by Damien Miller have been
> getting along just fine. we hereby cordially invite you to join the party!
> 
> 	http://violet.ibs.com.au/openssh/list.html
> 
> best wishes for the new year.
Have you, personally, ever tried to talk to Theo?  I know I'm not the
only one who has tried, and only gotten flames in response.  I don't
think someone like that should be the head of any project, and it's
truly impossible to work with such a... person.
   Now, if you come to tell me there's a way to actually discuss things
with ration human beings, not having to deal with flaming egomaniacs,
I am all ears!  I would love to have more people to work with, where
the people could actually remain civil.
> -d.
> 
> ---
> http://www.monkey.org/~dugsong/
-- 
 Brian Fundakowski Feldman           \  FreeBSD: The Power to Serve!  /
 green at FreeBSD.org                    `------------------------------'

In message <Pine.BSF.3.96.1000103022509.7881A-100000 at
fledge.watson.org>, Robert
 Watson writes:
>I agree entirely.  I'd love to see a free, BSD-licensed, SSH 2.x
>implementation out there.  The continuing emphasis on improving the
>non-standard, albeit widely deployed, SSH 1.x protocol seems to be a less
>useful allocation of resources.  While a free version of 1.x is extremely
>useful, it's not the end-all. :-)  If you can get people to upgrade to
Actually,  Markus' modifications for the 1.6 protocol contain elements that
may be reused in a SSH 2.x implementation.  I would not call it a waste
of time at all.  The diff is rather small,  more a necessary cleanup.

Greetings,
 Niels.

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

nuqneH,

David Rankin <drankin at bohemians.lexington.ky.us> said
:
> > Apart from standards-compliance, what does SSH2 buy you over a cleaned
> > up SSH1?
> 
> I know it's been mentioned already, but the #1 is you can do PAM 
> challenge/response authentication correctly.
TISAuthentication option works fine for me.
                                     _     _  _  _  _      _  _
 {::} {::} {::}  CU in Hell          _| o |_ | | _|| |   / _||_|   |_ |_ |_
 (##) (##) (##)        /Arkan#iD    |_  o  _||_| _||_| /   _|  | o |_||_||_|
 [||] [||] [||]            Do i believe in Bible? Hell,man,i've seen one!

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQCVAwUBOHNT26H/mIJW9LeBAQGScQP/b7pDSIl9euhFcNOrGn2koIXvruUwFhO6
kbw+G2EtmqgFSWiCECyrhDerFL51fT67uaGKPQtoQ6fmiZ6zAhbDiVGI3ASPoPnO
tDP4rgsiRNiAy3YTmooaBMbL+XmWTg+WYRlTUDeGLVnUQbOWVUNn3kL83P0K2ScP
iBMUOtLr8wc=VDHV
-----END PGP SIGNATURE-----