Linked by Robert Escue on Wed 4th Jun 2008 05:06 UTC
Thread beginning with comment 317409
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[12]: wow, you guys are pretty harsh
by mickrussom on Fri 6th Jun 2008 12:23
in reply to "RE[11]: wow, you guys are pretty harsh"
RE[13]: wow, you guys are pretty harsh
by Arun on Fri 6th Jun 2008 12:25
in reply to "RE[12]: wow, you guys are pretty harsh"
Yes, I've been trying like hell to get: 126134-03 withdrawn.
Its completely broken, breaks X-forwarding and in no way can you enable it with tricks, forcing IPv4, you name it, its broken.
Anyways as of 6/6/2008, its still there.
sigh.
Its completely broken, breaks X-forwarding and in no way can you enable it with tricks, forcing IPv4, you name it, its broken.
Anyways as of 6/6/2008, its still there.
sigh.
Where are the ZFS bugs? You keep brining up the wrong bug.







Member since:
2008-06-05
Porting a driver and actually making sure it release ready are very different things. Your ignorance is very evident as well. [/q]
So.... speaking of OpenBSD...
How come Solaris's SSH is so broken, much more broken than the OpenSSH port to Solaris (build from openssh.com or get from sunfreeware). No ForwardX11Trusted, PermitUserEnvironment is supported now but the --with-default-path is anemic and there's no proper way to set default environment vars for users (rsync via ssh fails without --with-rsync-path), no ControlMaster, etc.
And yet as mickrussom pointed out before, Sun broke X11 forwarding recently and apparently has yet to withdraw the patch. No one's bothered to set up an automated regression test for X11 forwarding via SSH yet?
Yeah, Sun sure has something to teach the OpenBSD people about release readiness.