search for: use_sia

Is the following (from configure.in) intended: *-dec-osf*) if test ! -z "USE_SIA" ; then AC_MSG_CHECKING(for Digital Unix Security Integration Architecture) should that be "$USE_SIA" or similar or what is the point of testing a constant string for being zero length... The reason I ask is the for complex reasons we don't want SIA enabled on Tru64 since it...

...nted me so far. > > It would be great if I could get some feedback on how > http://www.mindrot.org/misc/junk/openssh-SNAP-20000629.tar.gz > works on Solaris, Irix 6.x, HPUX, AIX, Tru64 and SCO. > > BTW this snapshot contains DEC OSF/Tru64 SIA support, enable it > using "USE_SIA=1 ./configure [options]". I would like some feedback > from DEC users as to the correctness of this code (as I know nothing > about SIA). > > -d > > -- > | "Bombay is 250ms from New York in the new world order" - Alan Cox > | Damien Miller - http://www.mind...

...9;ve got patches for two existing files: auth-passwd.c sshd.c I've also got two new files: auth-sia.h auth-sia.c How should the patches and files get packaged together? (I'm not sure how to create a patch for a file where none existed before). On Tru64 UNIX systems, the USE_SIA macro needs to be defined, and sshd needs to be built using -lsecurity. I don't know how to hack the configure process to make this happen. I'd like to learn, but I'd be happy not to have to learn also. :-) Thanks.

Sorry if this is stuff that's been talked about before. If it is, just ignore me. I'm curious to know why Portable OpenSSH doesn't include @bindir@ in the _PATH_STDPATH. This would save most installers of portable OpenSSH from having to --with-default-path=$PREFIX/bin in order to ensure that scp will work properly. This would also, I imagine, save quite a lot of hassle for

what do you think about this patch to add the path to scp to _PATH_STDPATH? is there a better or cleaner way to do this? i'm hoping to ward off 'scp doesn't work' questions for the next release. i did *not* add this to a --with-default-path path, because if a user specifies that, they should control its value completely. Index: Makefile.in

Just today I compilied openssh-2.1.1p1 on Debian Slink and Potato both to come out with the same problem. I am compiling them with openssl-0.9.5a.. The configure line I use for openssh is below: ./configure --sysconfdir=/etc/ssh --prefix=/usr --with-ssl-dir=../openssl-0.9.5a So I compile, do a make install restart the sshd daemon and everything seems fine. Then when I do a w at the prompt

...t${ac_exeext}; then +if { (eval echo configure:1429: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then rm -rf conftest* eval "ac_cv_func_$ac_func=yes" else @@ -1478,7 +1480,7 @@ # This is untested if test ! -z "USE_SIA" ; then echo $ac_n "checking for Digital Unix Security Integration Architecture""... $ac_c" 1>&6 -echo "configure:1482: checking for Digital Unix Security Integration Architecture" >&5 +echo "configure:1484: checking for Digital Unix Security...

...t${ac_exeext}; then +if { (eval echo configure:1484: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then rm -rf conftest* eval "ac_cv_func_$ac_func=yes" else @@ -1546,7 +1548,7 @@ # This is untested if test ! -z "USE_SIA" ; then echo $ac_n "checking for Digital Unix Security Integration Architecture""... $ac_c" 1>&6 -echo "configure:1550: checking for Digital Unix Security Integration Architecture" >&5 +echo "configure:1552: checking for Digital Unix Security...