search for: potterveld

OK, I got a chance to try out the Tru64 patch for privsep. I applied the patch to 3.4p1. Partial success, in that it now works for me for logins to "root". Logins to ordinary accounts fail after authentication, when trying to set tty characteristics. See the excerpt from the debug messages below. This is for Tru64 V4.0F (with enhanced_security turned on, obviously.) I guess it's time

...my drives known to be bad? Is there a list somewhere? Q: What are the workarounds for RH and windows alluded to? I have some utilities downloaded from IBM, which I vaguely remember may let me change/disable cache modes. I'm gonna shut down now and give that a try. Thanks for any help... David Potterveld

...things in. I suspect that what happens is, the privileged process forks, sets up the pty, and becomes the user all on its own, and then the privileged process starts doing the sia stuff. But its just a suspicion... I need to read the code carefully myself to understand what's happening. David Potterveld Argonne National Laboratory

...macro is: #define PRIVSEP(x) (use_privsep ? mm_##x : x) As far as I can tell, this merely calls different routines, depending on use_privsep. I don't see how the user's sshd process can revert to being root. If that were so, then the whole idea of privilege separation is bogus. David Potterveld Argonne National Laboratory

Tru64 patch will not make it into 3.5 (this is final) due to lack of willing people to test. I have given the Tru64/osf1 community almost a month to test it. And *ONE* person came forward to give me verification. And don't give me shit about "I don't have time." The person who tested it was LEAVING his employer with Tru64. He found time. IT IS YOUR GAWD DAMN PLATFORM. IF

Dear openssh-unix-dev; I recently downloaded the tarball openssh-3.4p1 and built it for my Tru64 Unix ( OSF/1 ) 5.1a system. My configure statement is: ./configure --prefix=/usr/local/security/tools/openssh-3.4p1 \ --exec-prefix=/usr/local/security/tools/openssh-3.4p1 \ -with-ssl-dir=/usr/local/security/tools/openssl-0.9.6g \ -with-zlib-dir=/usr/local/compress/tools/zlib-1.1.3 \

I don't know if this is a bug or a limitation in ssh2 but I am unable to get get an xdm (or gdm) login on my machine at home through an ssh tunnel through our firewall at work. Should this be possible using ssh port forwarding? Please reply to me at: rwk at americom.com Thanks, Dick