similar to: OpenSSH-1.2.3 AIX scp failure

Please find attached a patch I put together to provide some useful extras using OpenSSH 2.2.0p1 under AIX. I have been forced to write these to allow OpenSSH to conform to our local security policy and to aid our user administration department. Please note that in testing of this latest release we found "useLogin yes" to be broken again. Since login provides no extra functionality in

Hi, If I enable "UseLogin" under AIX, I get the following message upon login: /dev/pts/2: 3004-004 You must "exec" login from the lowest login shell. The manpage states: "In order to preserve the integrity of the system, only one session at a time is allowed to be logged in to a port. This means that the login command entered from the shell prompt cannot succeed,

Folks, I noticed that whenever I scp'ed a file to my test server (running OpenSSH 2.1.0p2, and then tested with p3) it was created owned by root. /home/me $ ls -al .profile -rwx------ 1 me group 1056 Jan 18 1999 .profile /home/me $ scp .profile me at server:test me at server's password: .profile 100%

Hi. New (2.1.1p1) login code is nicer on AIX (4.2.1.0.06). Thanks. A couple of issues, though, which I haven't really dug into yet. I'm wondering if anyone else has seen them? If not, I'll investigate & report. 1. If I set "UseLogin" to "yes", everything seems fine except that the authentication agent forwarding doesn't work. The "SSH"

>This issue has actually cropped up again recently in my testing. When I >do use Solaris login (UseLogin yes), a ton of the important environment >variables (like TERM, etc) don't get passed. Is that normal behavior? Looking at the source os session.c it is obvious that when you use login the environment is not passed: execl(LOGIN_PROGRAM, "login",

Hello Ive downloaded OpenSSH 4.1p1 from the portable openssh web pages... Compiled it up for an AIX 5.1 host (with latest IBM maintenance patches applied) using defaults in all cases. When doing a successful SSH authentication it places an entry into /etc/security/failedlogin as well as /var/adm/wtmp Ive also tried adding "UseLogin yes" to the sshd_config PAM ISNT configured (infact

I'm still a bit confused as to how control-d is interpreted in ssh vs telnet. The only thing I can figure is that telnet traps control-d as User_Exit or USER_Logout and ssh interprets it as EOF. If EOF is triggered, then the auditing subsystem doesnt care. The 'logout' command is only affected if you are NOT logged into the console. ==================== test_citi:/root # grep

I have an X11 application installed on a Solaris 5.7 server. ?The server runs the OpenSSH 2.3.0p1 daemon. ?I then SSH to this server from OpenSSH 2.3.0p1 under AIX with X11 forwarding enabled. ?I can run X utilities, such as xclock and xterm, without any problems. ?However, the X11 application I require (a Privacy Manager GUI) creates an empty window frame. If I telnet from the AIX server to the

Hi, If anyone has managed to get sshd to run as a subsystem in the System Resource Controller under AIX 4.3.3 (a la mkssys), then please let me know how you did it... I can mkssys and startsrc it, but it dies immediately, leaving a child sshd running with another PID than startsrc reported, and lssrc reports sshd inoperative. Is sshd a process that should stay in foreground, not forking? Or does

Hi, I have been written an small script for test the use these commands. I had done massive test with commands, but I didn?t get success it. Any of the cases, I don?t listen nothing on channel that call 2100 extension. I dial 2100 extension through an cisco phone 7912 with SIP, also I dialed through ATA SIP (Linksys PAP-2). I?m using Asterisk 1.2.7.1 and ztdummy driver, linux kernel 2.6.11.4. I

-- | "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) ---------- Forwarded message ---------- Date: Fri, 9 Jun 2000 17:06:30 +0200 From: Markus Friedl <markus.friedl at informatik.uni-erlangen.de> To: BUGTRAQ at SECURITYFOCUS.COM, misc at openbsd.org,

OpenSSH's UseLogin option allows remote access with root privilege. 1. Systems affected: The default installation of OpenSSH is not vulnerable, since UseLogin defaults to 'no'. However, if UseLogin is enabled, all versions of OpenSSH prior to 2.1.1 are affected. 2. Description: If the UseLogin option is enabled the OpenSSH server (sshd)

Warren Young <wyml at etr-usa.com> wrote: > > The schily tools act as a container to publish the current code state. There is > > no such maintained web page. > > I was referring to the summary on the SourceForge page, where you just list the contents of the package without explaining why one would want to download it. I thought I don't need to make advertizing for

> Mar 13 12:01:48 whippet sshd[31644]: Received SIGHUP; restarting. > Mar 13 12:01:48 whippet sshd[31644]: RESTART FAILED: av[0]='sshd', > error: No such file or directory. My guess is that you started sshd using "sshd" (either from within /usr/local/sbin or with it in your PATH). > The sshd program is not named anything unusual, and is located in >

Hi I've finished and tested a patch to add src routines to openssh (based on the Redbook "Writing Reliable AIX Daemons") Since a few days I have the O.K. to post it on the list, but I still want to splitt my patch file into logical parts (SRC/Logging/Datatype fixes) Frank Datum: 06.09.2001 19:04 An: Denise Genty <genty at austin.ibm.com> Kopie:

On Apr 27, 2015, at 10:10 AM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > Warren Young <wyml at etr-usa.com> wrote: > >> I was referring to the summary on the SourceForge page, where you just list the contents of the package without explaining why one would want to download it. > > I thought I don't need to make advertizing for well

On Apr 27, 2015, at 9:07 AM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > > Heirloom added support for uname -S and for some linux ulimit extensions but > then stopped working on the code after a few months Ah. I had no idea it was in a state of disrepair. >> I see that you already wrote up the differences between osh and bosh in an earlier post. Is

Compile openssh-3.8p1 with gcc and the following flags --prefix=/tmp/build/sshd --with-ssl-dir=/tmp/build/lib --with-utmpx, no PAM. Everything complies correctly, and I changed sshd_config to use "UseLogin yes" When my client connects (using the newer ssh client too), I do not get the message that my password will expire in xx days, but sshd shows that it is picking up that info (next

Greetings, In order to use solaris's BSM (Basic security module) also called c2 audit, which logs specific kernel calls depending on your audit_control, I would need to use login(1) to log users exec calls and whatnot because Portable OpenSSH does not have <bsm/audit.h> support, now that would mean I would have to enable Uselogin in sshd_config in order for that to work. I am running

All, I'm using the Powercom driver from 2.2 (not the one recently mailed to thelist). Since it's a KIN2200AP, I'm using the driver settings right from the manpage. All the values look "sane" when I'm on-line, but note some of the odd values (<-- Here) when on battery: Also, does anyone know if this UPS supports logging of the "boost" or