similar to: [Fwd: Serious Bug Report: OpenSSH]

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

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

Hi, i have a minor Problen with Samba 1.9.16p11 under RedHat 4.2 and samba 1.9.18 under RedHat 5.0. Getting the shares from NT or w95 are ok but in the messages log file i got tons of these messages: Feb 2 06:49:54 bell PAM_pwdb[3520]: get passwd; pwdb: structure is no longer valid Feb 2 06:49:59 bell last message repeated 93 times Feb 2 06:49:59 bell PAM_pwdb[3520]: 1 authentication

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

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

I just went through upgrading from 2.0.7 on Redhat 7.0 using the binary RPM provided by samba.org and noticed a problem with the swat install. It seems that the swat binary in the RPM is built to look for it's supporting files in /usr/share/samba/swat whereas the RPM installs said files in /usr/share/swat. This results in the following error message when you try to access swat: 400 Server

I am having a problem similar to the one that Jason Gerrity is having with authentication. Sometimes people are unable to access drives on one of our unix servers from an NT machine. They are prompted for their password and when they enter it they get the message "Incorrect password or unknown username." These are people that have permissions on unix and can usually access these

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, 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, 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 executing a Repeated Measures Analysis of Variance with 1 DV (LOCOMOTOR RESPONSE), 2 Within-Subjects Factors (AGE, ACOUSTIC CONDITION), and 1 Between-Subjects Factor (SEX). Does anyone know whether the between-subjects factor (SEX) belongs in the Error Term of the aov or not? And if it does belong, where in the Error Term does it go? The 3 possible scenarios are listed below: e.g., 1.

I have executed a Repeated Measures ANOVA with one DV (latency) and one within subject factor (acoustic condtion: 3 levels) by bootstrapping my sampling distribution of F from the empirical sample distribution. I chose to resample because the sample distribution deviates from normality a lot. The overall F is significant and now I wish to decompose this with contrasts to ask if latencies to

Im running an accounting package (Sage Businessworks) and I'm running into issues with file locking with this program when I put the businessworks data files on a Samba file share. I'd like to get it off a NT file share if at all possible as Im about to decommission our NT server. Im running Samba 2.0.6 Im seeing errors from any machine accessing the Accounting data: ==> log.ryan

Hi there I'm running a samba cvs server in a windows domain with a W2K PDC. I want to authenticate windows users through ssh. I'm able to login with a windows user to the server on the server himself but when I want to login via a windows client It doesn't work. The connection is refused. Could it be something mis configured in my ssh pam module. This is my pam ssh module PAM

The winbind now works...my getent passwd & groups returns the domain users/groups What should be the next step? my clients (Win2K & Win9x) are still prompting for a password and I cannot login to my linux box using DOMAIN*domainuser. Must I add each domain user as a user on the linux box? Regards Winston Nimchan -----Original Message----- From: Sean Trammell

I tried upgrading from samba 1.9 to 2.0 on two seperate RedHat servers, and after both upgrades nobody could get authenticated. The windows boxes had the registry hacks to turn off encrypted passwords, and I'm authenticating out of passwd+shadow. I found many similiar posts on DejaNews and in the samba mailing list archives. I broke out strace and found the problem. Samba 2.0 tries to

Hello, I am have some interesting problems with the pam_winbind portion of samba 3.1. wbinfo -u and getent passwd works but when I login I get the following messages in /var/log/messages. Jan 5 11:09:36 hermes pam_winbind[9014]: write to socket failed! Jan 5 11:09:36 hermes pam_winbind[9014]: internal module error (retval = 3, user = `CSQ+shane' Jan 5 11:09:36 hermes PAM_pwdb[9014]: check

This might have been covered before and I've missed it. If so, sorry in advance. The file sshd.pam.generic didn't work for me on Linux RH6, I guess it's a Solaris file. Instead I copied the file /etc/pam.d/rlogin to /etc/pam.d/sshd . I wonder if this isn't a good way to go about things anyway, have an install target that does just that? Perhaps the rsh file is more appropriate