similar to: updated SuSE spec file

Howdy, The string of notices on BugTraq about RSAref being vulnerable to overflows has me concerned. After trying to sort through all the messages, I can't figure out whether I need to update OpenSSL (a check of their website indicates no new patches), OpenSSH, both, or neither. I am aware there is no known exploit for it yet. I could be a bad boy and just run all

Howdy, It seems that even when specifying the --with-tcp-wrappers configure flag, the LIBWRAP define in config.h never gets #define'd and -lwrap never gets added to LIBS in the Makefile. To make sure I wasn't dealing with a stale configure file, I ran autoconf on configure.in to roll a new configure. I also don't see anything wrong with the --with-tcp-wrappers defined in

Howdy, It seems that as of 1.2pre15, ssh-add no longer looks for ssh-askpass in the usual place. (I noticed this both in the source code, ssh-add.c, and to some degree in the ChangeLog.) If you're like me and keep ssh-add in your Autostart folder in KDE, chances are upgrading to 1.2pre15 will result in no longer getting the nice Gnome widget we've come to know and love when

Attached is a spec file for OpenSSH on SuSE 6.4 and 7.0 systems. It differs from the current spec file in the following details: - Only one rpm file is created containing client and server files. - PreReq `openssl-devel' is changed to `openssl'. - Path '/usr/libexec/ssh' is changed to '/usr/lib/ssh' for ssh-askpass and gnome-ssh-askpass. The resulting

Howdy, Well, I finally made it through a complete build of OpenSSH on Solaris 7/x86. I've included a few notes below. Most of them are either simple enough or too complex (i.e. I'm not sure how to do it without breaking other platforms) to generate patches for here. 1) _PATH_DEVNULL, _PATH_UTMP and _PATH_WTMP aren't defined anywhere, since Solaris doesn't appear

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just uploaded openssh-1.2pre16 to: http://violet.ibs.com.au/openssh This is mainly a bugfix release, it should fix some of the recurrent compile problems that have been reported to the mailing list and to me (the __P() stuff on Solaris for example). Full changelog: 19991207 - sshd Redhat init script patch from Jim Knoble <jmknoble at

Attached is a small patch that should fix most of the problems reported. I am adding a recommendation to use GNU make to the INSTALL document. Regards, Damien -- | "Bombay is 250ms from New York in the new world order" - Alan Cox | Damien Miller - http://www.mindrot.org/ | Email: djm at mindrot.org (home) -or- djm at ibs.com.au (work) -------------- next part -------------- Index:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just uploaded openssh-1.2pre15 to http://violet.ibs.com.au/openssh/ Changes: - Merged big source cleanup from OpenBSD CVS. All the source now conforms to: http://www.openbsd.org/cgi-bin/man.cgi?query=style&apropos=0&sektion=9&manpath=OpenBSD+Current&format=html - Added BSD compatible install program - More

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just uploaded 1.2.1pre22 to: http://violet.ibs.com.au/openssh/files/ This release consists of portability fixes and cleanups. It also resolves two issues which may have caused security problems - If you OS header files did not define PATH_STDPATH, then an unsafe path was used by default (it contained an implicit '.'). Thanks

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just uploaded 1.2.1pre22 to: http://violet.ibs.com.au/openssh/files/ This release consists of portability fixes and cleanups. It also resolves two issues which may have caused security problems - If you OS header files did not define PATH_STDPATH, then an unsafe path was used by default (it contained an implicit '.'). Thanks

Hi all. It's nice to see that AIX support (unintentionally?) is getting better and better. :) Attached is a patch against pre14 that fixes AIX support. All that is left, basically, is a replacement for the /dev/urandom way of getting entropy. ... A completely different thing... how about DCE support? I was thinking of adding some dce code to sshd that: 1. Attaches credentials based on

Can anyone using PAM and rsa-rhosts authentication replicate this? Damien -------------- next part -------------- An embedded message was scrubbed... From: Adrian Baugh <adrian at merlin.keble.ox.ac.uk> Subject: Serious Bug Report: OpenSSH Date: Wed, 1 Dec 1999 02:38:56 +0000 (GMT) Size: 3926 Url:

With the sshd in recent releases of OpenSSH, some Red Hat Linux systems complain about ulimit trying to raise a limit when logging in via ssh. The problem is that packages/redhat/sshd.pam doesn't do limit checking for an sshd session. The attached patch adds the pam_limits module to the sshd session, which checks for limits set in /etc/security/limits.conf. This works on Red Hat Linux 5.2

On Thu, Jun 19, 2014 at 2:51 PM, Andrew Rae <A.M.Rae at leeds.ac.uk> wrote: > Hi all, > > wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. I'd say this is an excellent place to start. I'm getting some similar results here with the precompiled

> Hi all, > > wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. > > below are results of me testing - i did each a few times to make sure they are valid results. > > hope it helps identify something that's gone awry ? > so far, 6.03

I just picked up 3.10-pre15 and the "PXELINUX corrupts graphic filename referenced from DISPLAY file" bug is zapped. Yipee! Thanks hpa. And Arwin too, if that 'xor esi,esi' was the crux. However, LOCALBOOT -1 and LOCALBOOT 0 don't work the same as they did for me in 3.07. :-( 3.07: LOCALBOOT -1 apears to work as I have a hard disk listed in bios boot order after the

From: Ralph Angenendt <ra+centos at br-online.de> > If you can read binary :) > The script section of the glibc RPM is a very simple one: > [angenenr at shutdown dict]$rpm -q --scripts glibc > postinstall program: /usr/sbin/glibc_post_upgrade.i686 > postuninstall program: /sbin/ldconfig > And I cannot find Documentation for glibc_post_upgrade at the moment, a >

> It looks like the passenger RPM has a script importing the GPG key. Check using "rpm -q --scripts passenger". >From what I can see, it doesn't: # rpm -q --scripts passenger postinstall scriptlet (using /bin/sh): if /usr/sbin/sestatus | grep 'SELinux status' | grep -q enabled; then actual_selinux_variants=; for selinux_policy_file in /etc/selinux/*/policy;

hi all, in case someone else runs into it, it is the opfed-scripts rpm that has a postinstall and postuninstall script that changes the yum.conf (bad, mellanox, bad) for a pure/regular uninstall it works fine, but to swap ibutils from mlnxofed to ib stack from os, yum obviously doesn't know that the exclude will be removed. i've seen worse in vendor-provided rpms, but i guess it caught

Hello, I didn't try 6.02-pre15, I will do and I will post the results, my keyboard is a PS/2 model, the "legacy USB storage option" is enabled, I tried also an USB keyboard but there is no change, so it's not a keyboard problem, it probably something in syslinux ( ldlinux.sys ? ) who create a serious bug with my motherboard, I tried also with a USB HDD ( not a flash drive )