similar to: patch for getting 2.1.1p4 to compile on SunOS 4

Hi guys... Just wanted to see what is so different in BSD from Linux and had a quick look at the openbsd-compat directory (openssh-2.5.1p1). There is a REALLY obvious bug in bsd-misc.c, quoted below: #if !defined(HAVE_STRERROR) && defined(HAVE_SYS_ERRLIST) && defined(HAVE_SYS_NERR) const char *strerror(int e) { extern int sys_nerr; extern char *sys_errlist[];

perror is not fork-safe and so could deadlock. Instead open code a fork-safe version of perror. While this fixes the current behaviour, in the long term we'd like to capture the error message into the usual error mechanism, so this is not the full and final fix for this issue. Also this fixes the exit code to be 126/127 instead of 1. Thanks: Eric Blake --- TODO | 1

On 9/30/19 11:32 AM, Richard W.M. Jones wrote: > perror is not fork-safe and so could deadlock. Instead open code a > fork-safe version of perror. While this fixes the current behaviour, > in the long term we'd like to capture the error message into the usual > error mechanism, so this is not the full and final fix for this issue. > > Also this fixes the exit code to be

FYI >Path: news.uni-erlangen.de!uni-erlangen.de!newsfeeds.belnet.be!news.belnet.be!news.tele.dk!130.133.1.3!fu-berlin.de!server1.netnews.ja.net!news.gla.ac.uk!not-for-mail >From: Will Partain <partain at dcs.gla.ac.uk> >Newsgroups: comp.security.ssh >Subject: Re: Q: core dumped on keygen in Sol 2.6, ssh2.3.0p1, openssl-0.9.6 and zlib-1.1.3 >Date: 21 Feb 2001 12:27:24 +0000

Details of installation attached. Effect: when I build and test (with full path names) ssh in the openssh... directory, everything works fine. When I "install" it as per attached file into a test-directory and run it from there, there are 2 phenomena: either it just hangs, eating 96% of CPU or it dies with a Segmentation fault (this is what happens most often) Help needed

Hi there, everybody; As promised, here's the new version for my chroot patch. It applies cleanly over OpenSSH 2.1.1p4, and I'm attaching 2 versions: - openssh-2.1.1p4-chroot.patch-wc, is the chroot patch plus a "--with-chroot" patch for the "configure" script. - openssh-2.1.1p4-chroot.patch, is the same without the "--with-chroot" part. Have fun,

I'm trying to understand the rational behind the arc4random() and arc4random_stir() functions in the OpenSSH source tree. On a system that has a good random number generator, say an in kernel /dev/random what extra functionality is this stuff providing ? Would it be acceptable to replace the calls to arc4random() with reading from /dev/random and drop the arc4random_stir() all together ?

On 10/1/19 9:11 AM, Richard W.M. Jones wrote: > On Tue, Oct 01, 2019 at 08:24:33AM -0500, Eric Blake wrote: >>> +#else /* !HAVE_EXECVPE */ >>> + SET_NEXT_STATE (%.DEAD) >>> + set_error (ENOTSUP, "platform does not support socket activation"); >>> + return 0; >>> +#endif >> >> We probably ought to add a matching

Hi When I compiled sendmail v8.11.6 with LLVM 1.2, I found some variables with strange type, such as: %sys_errlist = external constant [0 x sbyte*] ; <[0 x sbyte*]*> [#uses=3] %tmp.24 = getelementptr [0 x sbyte*]* %sys_errlist, long 0, long %tmp.23 ; <sbyte**> [#uses=1] The process of getting these is: 1. entry sendmail-8.11.6 directory 2. make

I believe there is a problem with the openbsd-compat/bsd-arc4random.c file. If arc4random () is called without seed_rng having previously been called (eg if you run ssh-keygen -p ) then it does not in fact invoke seed_rng () if it is the first time. Instead it will invoke seed_rng every time BUT the first time. At least that is the way I read the code, and changing it as below allowed me to

https://bugzilla.mindrot.org/show_bug.cgi?id=2168 Bug ID: 2168 Summary: Fails to build after arc4random API change in OpenBSD Product: Portable OpenSSH Version: -current Hardware: All OS: OpenBSD Status: NEW Severity: minor Priority: P5 Component: Build system Assignee:

Howdy. I'm trying to get OpenSSH to work on Mac OS X which is basically BSD unix. I'm getting segfaults connecting to SSH1 servers (I have no SSH2 servers to test against so I'm not sure if it's common). I've followed the instructions on compiling at http://www.stepwise.com/Articles/Workbench/2001-03-21.01.html which essentially amount to ./configure

Hi, Yesterday I tried to replace the system openssl in a gentoo system with libressl. With openssh an interesting issue popped up: * RAND_bytes in libressl calls arc4random * arc4random is a compat function both in openssh and libressl * arc4random from openssh uses RAND_bytes So what's happening is a recursion. arc4random wants to use RAND_bytes and RAND_bytes wants to use arc4random. The

First error: head file related. Strangely, this code has been there a while, which makes me think that the HAVE_ARC4RANDOM is somehow now showing up as set whereas perhaps it didn't used to be. tfiala at tfiala2:~/lldb/svn/lgs/build$ make make[1]: Entering directory `/mnt/ssd/work/svn/lgs/build/lib/Support' llvm[1]: Compiling Process.cpp for Debug+Asserts build In file included from

Hi, I have some problem with running testsuites for samba. I use the dejaGNU 1.4.2 and latest 2.2.4 samba sources. What's wrong with my settings ? When I running runtest in testsuites directory I got: WARNING: Couldn't find the global config file. WARNING: No tool specified Test Run By eugene on Thu Jun 6 18:37:13 2002 Native configuration is sparc-sun-solaris2.8 ===

Hi. Here are the relevant details about the setup: SunOS 4.1.4 gcc 2.7.2.2 tcp wrappers 7.5 egd 0.6 (doesn't really come into play at compile time) The following only pertains to the compilation (and linking) stage. Code and patches are SunOS specific. -- The following functions are missing in SunOS: strerror, atexit, memmove. I wrote simple replacements in term of on_exit and bcopy

Hi, as I saw someone today pointing to a solution for protected directories in the recycle dir (thanks Ben!), I wanted to compile the modified recycle.c. I'm using Mandrake 9.0, I have kernel-source, kernel-header and all basic development tools installed, including the libtool package; I downloaded the Samba 2.2.7a sources, applied the patch, but I cannot compile the library. Following

I have just tarred up a snapshot and uploaded it to: http://www.mindrot.org/misc/openssh/openssh-SNAP-20000823.tar.gz The snapshot incorporates the last month's fixes and enhancements from the openssh-unix-dev mailing list and from the OpenBSD developers. In particular: - ssh-agent and ssh-add now handle DSA keys. NB. this does not interop with ssh.com's ssh-agent. (Markus Friedl)

v1 was posted here: https://www.redhat.com/archives/libguestfs/2019-September/thread.html#00337 v2: - Drop the first patch. - Hopefully fix the multiple issues with fork-safety and general behaviour on error paths. Note this requires execvpe for which there seems to be no equivalent on FreeBSD, except some kind of tedious path parsing (but can we assign to environ?) Rich.

I'm seeing some extremely odd behavior with solaris. I have a suspicion it's me, but here's the story and maybe someone can suggest an avenue of investigation. This seems to be happening with any release of openssh since at least 2.5.2p1. 1) Problem #1: If SSH protocol 1 is enabled then sshd segfaults right off. This turns out to be because the call to arc4random_stir is