similar to: [Bug 1875] New: Gentoo QA warning: net-misc/openssh-5.8_p1-r1: closefromtest.c:46: warning: implicit declaration of function ‘closefrom’

http://bugzilla.mindrot.org/show_bug.cgi?id=1345 Summary: closefromtest fails, sometimes Product: Portable OpenSSH Version: 4.6p1 Platform: amd64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Miscellaneous AssignedTo: bitbucket at mindrot.org ReportedBy:

http://bugzilla.mindrot.org/show_bug.cgi?id=1358 Summary: closefromtest fails, differently, sometimes Product: Portable OpenSSH Version: 4.7p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Miscellaneous AssignedTo: bitbucket at mindrot.org

Please pardon any user idiocy involved, but I applied the OpenBSD 3.4 patch to the 3.9 sources on both my i386 and sparc64 OpenBSD 3.4 boxes, and get the same error: cc -o sshd sshd.o auth-rhosts.o auth-passwd.o auth-rsa.o auth-rh-rsa.o sshpty.o sshlogin.o servconf.o serverloop.o uidswap.o auth.o auth1.o auth2.o auth-options.o session.o auth-chall.o auth2-chall.o groupaccess.o auth-skey.o

https://bugzilla.mindrot.org/show_bug.cgi?id=2681 Bug ID: 2681 Summary: postauth processes to log via monitor Product: Portable OpenSSH Version: 7.4p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: sshd Assignee: unassigned-bugs at

The snprintftest.c regression test in openbsd-compat/regress has a buffer overflow error, and an argument error in the calls to snprintf(), and vsnprintf(). On line 49 of snprintftest.c, the character buffer, b, is allocated at 5 bytes. However, in the calls to snprintf and vsnprintf, on lines 68 and 77 respectively, it is expected to place 11 bytes of data into the buffer. Which will result

Hello All, I'm using OpenSSH 4.3p2 in HP-UX 11.23. On running tusc (a tool to trace system calls and signals) on sshd, I found lot of close calls upto 2047. Those close calls try to close a non-opened file descriptor and results in an error. This behaviour is seen only from OpenSSH 3.9 where closefrom() call is introduced to close the file descriptors before re-exec. The fix is to check

Trying to build xapian+omega on tinycorelinux. I followed the install guide and get pass configure/make/make install/omindex, but when I try to run omega "P=search term", I received the following message: # ./omega.cgi 'P=small' Content-Type: text/html; charset=utf-8 Illegal instruction # Attached is the config.log . Make check in omega-core/tests/ shows a lot of failed

On Sun, 2018-01-07 at 18:41 +0000, halfdog wrote: > Hello list, > > I created a page to demonstrate, what would happen when chroot > root directory is writeable. In fact, code execution is possible > already, when only /etc and /bin are writable. I also tried to > escape the chroot jail, but that did not work for non-root users. > > As the 2009 CVE activities mention,

Hi, As I understand the "ForceCommand" in the sshd_confing file is meant to ignore any command supplied by the client, but if user's home is shared by server and client machines over network (ex. NFS) then user can still put something else into ~/.ssh/rc file and overcome this limitation. Is it possible to disable execution of the ~/.ssh/rc file in such a case? Thaks, Mike

https://bugzilla.mindrot.org/show_bug.cgi?id=1007 --- Comment #16 from Darren Tucker <dtucker at zip.com.au> 2008-01-01 04:57:07 --- Created an attachment (id=1431) --> (http://bugzilla.mindrot.org/attachment.cgi?id=1431) Make ssh-rand-helper close all fds above STDERR Random thought: I wonder if some commands are making unwarranted assumptions about the descriptors they inherit?

Release Announcements --------------------- This is the latest stable release of the Samba 4.11 release series. Please note that there will be *security releases only* beyond this point. Changes since 4.11.13 --------------------- o G?nther Deschner <gd at samba.org> * BUG 14166: lib/util: Do not install /usr/bin/test_util. o Philipp Gesang <philipp.gesang at intra2net.com>

Release Announcements --------------------- This is the latest stable release of the Samba 4.11 release series. Please note that there will be *security releases only* beyond this point. Changes since 4.11.13 --------------------- o G?nther Deschner <gd at samba.org> * BUG 14166: lib/util: Do not install /usr/bin/test_util. o Philipp Gesang <philipp.gesang at intra2net.com>

On 8/1/19 4:15 AM, Richard W.M. Jones wrote: > On Thu, Aug 01, 2019 at 10:06:01AM +0100, Richard W.M. Jones wrote: >> As far as I can see Haiku (hrev52698) has O_CLOEXEC but NOT >> SOCK_CLOEXEC. As this version is a little old I'll do an update and >> see if newer versions support it. > > I'm on hrev53313+1 which also doesn't appear to have SOCK_CLOEXEC

https://bugzilla.mindrot.org/show_bug.cgi?id=2394 Bug ID: 2394 Summary: Provide a global configuration option to disable ControlPersist Product: Portable OpenSSH Version: 6.8p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh

https://bugzilla.mindrot.org/show_bug.cgi?id=1643 Summary: Set FD_CLOEXEC on client socket Product: Portable OpenSSH Version: 5.2p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy: jchadima at

Dear All, X.509 certificates support for OpenSSH version 6.0p1 was published. I brief new version include : - support for Android platform; - engine implementation is now considered stable; - various regression test improvements including fixes for OpenSSL FIPS enabled 1.0.1 stable release and korn shell Yours sincerely, Roumen Petrov -- Get X.509 certificates support in OpenSSH:

Hello, I''ve been working for a few days on a problem which, after tracking it down, seems to be related to unicorn. I''m hoping that somebody might be able to help with information about what''s going on. In the Rails 3 application that I support, we sometimes fork during a web request in order to do background processing behind the scenes without the user (and the

On Tue, Sep 10, 2013 at 2:20 PM, Dennis Jenkins <dennis.jenkins.75@gmail.com > wrote: > On Tue, Sep 10, 2013 at 1:34 PM, Doug Goldstein <cardoe@gentoo.org>wrote: > >> A suggestion would be to make sure that you have all the necessary >> kernel options enabled. You can check with: ebuild >> /usr/portage/app-emulation/libvirt/libvirt-1.1.2-r1.ebuild setup clean

On Tue, Sep 10, 2013 at 1:34 PM, Doug Goldstein <cardoe@gentoo.org> wrote: > On Tue, Sep 10, 2013 at 9:09 AM, Dennis Jenkins > <dennis.jenkins.75@gmail.com> wrote: > > Yeah our security people got a bit over zealous. That's being rectified. > > :) > > > > TL;DR: My container is configured to use "br0" for its networking. "br0"

OpenSSL 1.1.0 has deprecated this function. --- configure.ac | 1 + openbsd-compat/openssl-compat.c | 2 ++ openbsd-compat/openssl-compat.h | 4 ++++ 3 files changed, 7 insertions(+) diff --git a/configure.ac b/configure.ac index 3f7fe2cd..db2aade8 100644 --- a/configure.ac +++ b/configure.ac @@ -2710,6 +2710,7 @@ if test "x$openssl" = "xyes" ; then ])