similar to: how to determine the login shell?

Hi, Is it possible to determine the login shell (eg, whether it's /usr/bin/ksh or /usr/ace/prog/sdshell) from the sshconnect2.c? Is there a function call I can do to get the authctxt->pw->shell for example or would I need to do something like a packet_get_string? TIA. _________________________________________________________________ MSN Photos is the easiest way to share and

Here are some patches to re-enable support for AIX's authenticate routines. With them, ssh will honor locked & unlocked accounts, record successful and unsuccessful logins, and deny accounts that are prohibited to log in via the network. Tested with AIX 4.3. It also includes a fix for handling SIGCHLD that may be needed for other platforms (HP-UX 10.20, for example). If I get the time

Hi ! Here's a patch to add remote port forwarding support (protocol 2) for openssh. I have tried to test that it works like it should but a more thorough testing is needed. This patch adds both client/server support. The patch should be applied to openssh-2.1.1p4 source tree. Also included is a PortForwarding sshd_config option, new ./configure option --disable-forwarding that should make it

On Fri, Apr 24, 2015 at 08:54:48AM -0400, Pete Geenhuizen wrote: > Even though Solaris started using ksh as the default user environment, > almost all of the start scrips were either bourne or bash scripts. With > Bash having more functionality the scripts typically used the > environment that suited the requirements best. Bash is a better command shell for many people, but ksh

On Fri, Apr 24, 2015 at 08:32:45AM -0400, Scott Robbins wrote: > Wasn't Solaris, which for awhile at least, was probably the most popular > Unix, using ksh by default? Solaris /bin/sh was a real real dumb version of the bourne shell. Solaris included /bin/ksh as part of the core distribution (ksh88 was a part of the SVr4 specification) and so many scripts were written with #!/bin/ksh at

I was testing the Linux port of 2.1.0p2 and noticed that the F-Secure SSH client for Windows 4.0 couldn't successfully connect using its secure file-transfer facility. The server log reported that authentication was successful, then the log left off with a semi-cryptic "subsystem request for sftp" line. After that, nothing. Poking around the source, I found this little routine in

On 04/24/15 06:57, Pete Geenhuizen wrote: > > On 04/24/15 06:07, E.B. wrote: >> I'm sure most people here know about Dash in Debian. Have there >> been discussions about providing a more efficient shell in Centos >> for use with heavily invoked non-interactive scripts? >> >> With sh being a link to bash in Centos I don't know if it would >> explode

It was the mid/late-90s, but I seem to recall Bourne being the default shell, although sh/ksh/csh were all available with a typical install. On Fri, Apr 24, 2015 at 8:32 AM, Scott Robbins <scottro at nyc.rr.com> wrote: > On Fri, Apr 24, 2015 at 08:02:56AM -0400, mark wrote: > > On 04/24/15 06:57, Pete Geenhuizen wrote: > > > > > >On 04/24/15 06:07, E.B. wrote:

On 04/24/2015 03:57 AM, Pete Geenhuizen wrote: > if you leave it out the script will run in whatever environment it > currently is in. I'm reasonably certain that a script with no shebang will run with /bin/sh. I interpret your statement to mean that if a user is using ksh and enters the path to such a script, it would also run in ksh. That would only be true if you

On Fri, Apr 24, 2015 at 03:15:27PM +0200, Joerg Schilling wrote: > Stephen Harris <lists at spuddy.org> wrote: > > > Bash was bigger than ksh in the non-commercial Unix world because of ksh88 > > licensing problems. Back in 1998 I wanted to teach a ksh scripting > > course to my local LUG, but AT&T (David Korn himsef!) told me I couldn't > > give

On Fri, April 24, 2015 12:04 pm, John R Pierce wrote: > On 4/24/2015 9:47 AM, Gordon Messmer wrote: >> On 04/24/2015 03:57 AM, Pete Geenhuizen wrote: >>> if you leave it out the script will run in whatever environment it >>> currently is in. >> >> I'm reasonably certain that a script with no shebang will run with >> /bin/sh. I interpret your

I have a few patches for AIX. The patchfile is attached below. The patch has been tested on AIX4.2 and AIX4.3. The patch is on openssh-1.2.1pre25, with openssl-0.94, using RSAref. 1) authenticate support - this function allows the system to determine authentification. Whatever the system allows for login, authenticate will too. It doesn't matter whether it is AFS, DFS, SecureID, local.

Using openssh-SNAP-20001016 all of our problems with hanging connections have gone away (woohoo!), and it seems to be working flawlessly, but I am seeing messages like this in syslog: Oct 24 16:57:48 dhumb301 sshd[17752]: error: channel 0: internal error: we do not read, but chan_read_failed for istate 8 Oct 24 16:57:59 dhumb301 sshd[17771]: error: select: Bad file descriptor Oct 24 16:58:30

Hello I have few questions about openssh... 1/ there is probably bug in auth-password.c in auth_password function if (pw->pw_uid == 0 && options.permit_root_login == 2) return 0; if (*password == '\0' && options.permit_empty_passwd == 0) return 0; /* deny if no user. */ if (pw == NULL) <----------- this should be first checked .... return 0; 2/ do I have

Hi, Just a usecase that I'm sure has been covered before but just in case its not an openssh solution would be very helpful. I was trying to install software on a server that was firewalled so no outbound http connections would work. I was also tunnelling via another server. Outbound ssh connections also were a convenient option. What would have been nice would be a remote version of

I'm sure most people here know about Dash in Debian. Have there been discussions about providing a more efficient shell in Centos for use with heavily invoked non-interactive scripts? With sh being a link to bash in Centos I don't know if it would explode if the link was changed to something else, but at least the scripts we made on our own that run certain services could be changed and

Pete Geenhuizen <pete at geenhuizen.net> wrote: > Initially Bourne was used because it was typically a static binary, > because the boot process didn't have access to any shared libraries. > When that changed it became a bit of a moot point, and you started to > see other interpreters being used. When dynamic linking was intruduced in 1988, people did kno know what we

Hi , I have posted DTrace script to snoop tcp traffic and also provided a wrapper script for it to filter out unwanted traffic. http://blogs.sun.com/roller/comments/raviswam/Weblog/tcp_snoop_using_dtrace Please let me know if you have any feedback/comments on this. Thanks Ravi

Hello Steve, Hello OpenSSH-portable developers, I am building OpenSSH for our (EBCDIC-based) BS2000 mainframe operating system, and I noticed you do the same for OS/390. Because my initial ssh port was based on IBM's OSS port (ssh-1.2.2 or some such), I thought it was fair enough to help with a little co-operation; we might come up with a unified EBCDIC patch which could be contributed to

Darren, > -----Original Message----- > From: Darren Tucker [mailto:dtucker at zip.com.au] > Sent: Thursday, June 17, 2004 11:08 PM > To: Scott Rankin > Subject: Re: SSH_MSG_USERAUTH_PASSWD_CHANGEREQ and 3.1.0 > F-SECURE SSH - Pr oces s Software SSH for OpenVMS > > > Scott Rankin wrote: > >>That will depend on which versions exhibit the problems. Is it >