similar to: OpenSSH snaps have sftp libedit (command line history/editing) support

Hi all. For those that didn't know it, the OpenSSH portable team has been collecting survey data about the platforms that it runs and the options that it is built with. Partitipation is entirely voluntary and is as simple as running "make send-survey" after building (see the INSTALL file for details and caveats). I've used the data to answer a couple of questions on this list

Hi all. Now that we have SSHDLIBS for the libraries required by sshd only, it's possible to remove some of the single-purpose variables from Makefile. If this is worth doing, the next step would probably be to move the OpenSSL libs into CRYPTOLIBS since binaries such as scp and sftp don't need to be linked with libcrypto. Index: Makefile.in

Moving s sccessful compole of 5.2.p1 from a Suse 10.3 x86-64 box to a Suse 11.1 x86-box created a build problem ./configure --with-libedit=/usr/lib64 checking for el_init in -ledit... no configure: error: libedit not found however libedit (amd el_init) certainly exist: ookpik:/data/openssh-5.2p1.test # l /usr/lib64/libedit* lrwxrwxrwx 1 root root 17 Apr 4 17:11 /usr/lib64/libedit.so ->

Hi, I've noticed that building 4.1p1 fails on FreeBSD 4.x if the libedit support is enabled by the "--with-libedit" configure option. I tried to build OpenSSH-4.1p1 under the following environment: CPU: i386 family OS: FreeBSD 4.11-RELEASE Compiler: gcc-2.95.4 (/usr/bin/gcc) ---- libedit: (located at /usr/lib/) Building fails with the following messages: ---------- gcc

https://bugzilla.mindrot.org/show_bug.cgi?id=2173 Bug ID: 2173 Summary: configure fails to find libedit in non-standard location Product: Portable OpenSSH Version: 6.2p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: Build system

Hi All. As I mentioned earlier, I've been having weird failures with both sshd and sftp. The sshd one turned out the be my fault (misplaced "}", grr) but the sftp one doesn't appear to be. The sftp regression tests fail on the current portable tree on Solaris and AIX (with my own mods to auth.c and regress/, but I don't think that's related). The test that fails is:

Hi, While installing libeidt in Ubuntu 12.0 I am getting the following message. I am not even able to edit the curses.h and stddef.h file. Kindly help. /usr/lib/gcc/i686-linux-gnu/4.6/include/stddef.h:353:23: error: conflicting types for 'wint_t' /usr/include/curses.h:241:18: note: previous declaration of 'wint_t' was here make[3]: *** [terminal.lo] Error 1 make[3]: Leaving

Hi all. The old (~3.6.x) PAM code used to send PAM messages to stderr, whereas the new generic loginmsg code sends them to stdout, and it sends an extra newline. I think stderr is probably right, but the extra \n should probably be removed either way. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with

Olli Savia wrote: > The attached patch is a port of the current CVS (2005-08-11) version > of OpenSSH portable to LynxOS. Could you consider adding it to the > future releases of OpenSSH? If the patch needs additional work, please > let me know. Looks mostly reasonable, some comments and questions below. > + AC_DEFINE(LYNXOS_BROKEN_SETVBUF, 1, [LynxOS has broken setvbuf()

Is there a problem with the snapshots? The newest one on ftp.ca.openbsd.org is a week old. -Daz. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.

Does anyone actually use sshd on a system that doesn't have socketpair? It's used elsewhere so the don't-have path seems like it'd never be exercised these days. Index: monitor.c =================================================================== RCS file: /usr/local/src/security/openssh/cvs/openssh/monitor.c,v retrieving revision 1.147 diff -u -p -r1.147 monitor.c --- monitor.c

I am just looking for a quick answer as to whether or not OpennSSH is compatible with Digital Unix Tru64 v 4.0F. Hing Fei Wong Systems Engineer Building 100, M1309 Valley Forge, PA Admin # 4-6242 -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Friday, June 23, 2006 3:53 AM To: Wong, Hing Fei Cc: www at openbsd.org Subject: Re: OpenSSH compatibility with

Hi All. As of now, openssh on AIX passes all regressions tests (and, yes, I just checked!), works with privsep, bugzilla has zero open AIX-specific bugs and IBM ship it essentially unmodified as a supported product. I think it's beyond "support underway" :-) -Daz. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69

Hi all. I was getting something working over socks5 and was trying to figure out why it kept using socks4. It wasn't, it was just a misleading debug message.... Patch applies to either OpenBSD or Portable. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience

Hi All. Right now, if OpenSSH is configure'ed --with-kerberos5 and the system has a krb5-config that's not in /usr/local/bin then configure won't find it. The attached patch changes this so krb5-config will be used if it's anywhere in the path (although if it exists in the directory specified by --with-kerberos5= then the user-supplied path will take precedence). You will

Hi All. The attached patch speeds up the dynamic forwarding regression test: * moves starting the test sshd to the outer loop. * kills the sleep of when it's no longer required. -Daz. $ time PATH="`pwd`:$PATH" sh ../regress/test-exec.sh `pwd` \ ../regress/dynamic-forward.orig.sh ok dynamic forwarding real 0m54.585s user 0m5.760s sys 0m0.370s $ time

"DiNisco, Jeff" wrote: > I read in the change log that you fixed a bug that denies access to > accounts with locked passwords. My environment is dependent on public > key authentication. The account used does not have a person associated > with it but rather a service. I want to keep the password locked. Is > there a way to turn this fix off? What platform are we

Hi All. While working on something I noticed core dumps from sshd. They don't seem to be related to what I was working on. It's from the process forked to run the shell. Just after the fork, fatal_remove_all_cleanups() is called, which looks like: fatal_remove_all_cleanups(void) { struct fatal_cleanup *cu, *next_cu; for (cu = fatal_cleanups; cu; cu = next_cu) {

Hi. I made a regression test to catch the crash-on-sighup error that 3.6.1p2 had on a couple of platforms where it would not restart correctly. It's almost entirely code stolen from other tests. I verified it works by breaking saved_argv (the actual problem was not consistent on most platforms). I'd like it to suggest it be included in both the OpenBSD and -portable test suites. --

lambert lau wrote: > I did try the chsys command and it worked, an lssrc > showed it subsystem as active for a while but the SRC > stopped responding a short while later. I then ran > chssys -s prngd -a '-D' which had no effect. I get a > message telling me that the System Resource Controller > daemon is not active. "-D" the option to prevent *sshd* from