similar to: [PATCH]: openssh.spec file for SuSE 6.4 & 7.0

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

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:

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

-----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

-----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

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

-----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

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

Howdy, The following patch should be applied if you're building a SuSE-style RPM with the spec file included in the pre15 tarfile. I've made some changes since the copy that went out with pre15, and I've been a little lax in sending the updates up. Namely, one of the fixes includes not making symlinks part of the package itself. They are now done with a postinstall

I am taking the liberty of forwarding this message to the list. I am not subscribed to it. If you want to reply to me, please send email to faheem at email.unc.edu Thanks, Faheem Mitha. ---------- Forwarded message ---------- From: Faheem Mitha <faheem at email.unc.edu> Newsgroups: comp.security.ssh Subject: installing OpenSSH rpm on SuSE 6.2 Dear people, I tried

I have a couple of questions regarding openssh.spec and the rpm that gets generated from it. I am using 2.3.0p1 1. Why is openssl a prereq? openssh statically links to openssl during build by default (rightfully so, you don't want your security library a shared object if possible) 2. I don't understand the following line in the spec file during the install step (it makes it not build for

Tim, I reported a protocol data stream error on 9/8/2002 Deatils are in my postes at that time rsync still fails everytime I run it. This time I added three v's as you just suggested and rsync just hung with two tasks in execution thus: root 3178 0.1 0.9 1796 868 pts/1 S 09:57 0:00 /usr/bin/rsync -vvva --delete --exclude=root/snapsh root 3179 0.0 0.6 1628 632 pts/1

Hello I have this problem: I make my own php rpms, base on src.rpm from CentOS but with my patches (more options included). I have built it on my machine originally but now I want make it in mock environment. I solved almost everything but Firebird support for 64bit arch. Original RPM from http://www.firebirdsql.org/ are made with amd64 arch but my php is x86_64. And I don't know how to

https://bugzilla.mindrot.org/show_bug.cgi?id=1731 Summary: Obsolete BuildPreReq in contrib/redhat/openssh.spec Product: Portable OpenSSH Version: 5.4p1 Platform: Other OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: Miscellaneous AssignedTo: unassigned-bugs at mindrot.org

Hi, I have been making an RPM of FLAC to bundle with GStreamer. In order to get it working I had to make some rather hackish solutions in the SPEC file. The flac Makefile does to build into the correct directories while creating an RPM for some reason. I have attached the SPEC file I ended up with if it is of interest. Of course it didn't help me much cause it turned up we had a bug in the

(I'm using RedHat 6.2 and openssl-0.9.5a-3) After rebuilding binary RPMs using openssh-2.5.1p1-1.src.rpm, I was unable to ssh in to a system upgraded to the new openssh-server-2.5.1p1.rpm After the failure, /var/log/messages on the destination indicated lots of PAM errors of the form "sshd[22814]: PAM [dlerror: /lib/security/pam_stack.so: can not open shared object file: No such file

The packaging/lsb/rsync.spec file is broken as shipped: It has a "Sept" month (rpmbuild here takes only 3-letter month names), and RH gzips the manpages, so the %files list can't find them. I also added doc/README-SGML and doc/rsync.sgml to the %doc files. Patch follows. Thanks for all the good work! --- rsync-2.5.6/packaging/lsb/rsync.spec.orig 2003-01-28 06:28:35.000000000 +0100

Hello all, There are two issues in OpenSSH RPM Red Hat spec file (against 2.2.0p1): 1. /etc/rc.d/init.d/sshd uses 'success' and 'failure'. These don't work in Red Hat 5.2; else the spec file is fine. Initscripts requirement (for the one in RH60) added. 2. If you're upgrading over SSH ltd's ssh-server, the server will be stopped and sshd removed from chkconfig

. . . . hmod a+x mkdiskimage make -C sample all make[1]: Entering directory `/usr/src/redhat/BUILD/syslinux-2.08/sample' pngtopnm syslogo.png | \ ../ppmtolss16 \#000000=0 \#d0d0d0=7 \#f6f6f6=15 \ > syslogo.lss /bin/sh: pngtopnm: command not found ../ppmtolss16: stdin is not a PNM file at ../ppmtolss16 line 215. make[1]: *** [syslogo.lss] Error 255 make[1]: Leaving directory