similar to: Selective and efficient logging of auth/connection information

(Shame on me: wrong filename in last posting, now here are correct diffs) in contrib/solaris/ (openssh-SNAP-20011017.tar.gz) 1) buildpkg.sh makes wrong link for /etc/init.d/opensshd 2) /etc/init.d/opensshd has not-working killproc here my version tested on Solaris 2.4 and 8 (no pgrep with solaris 2.4, XARGS was undefined, simpler syntax) J?rg --- contrib/solaris/buildpkg.sh Fri Oct 12

Can someone else from the Solaris realm that uses our package system verify that this should be done? It looks right, but I want another opinion before commiting. - Ben > On Wed, 27 Feb 2002, Antonio Navarro wrote: > >> Hi Ben, >> >> I have made some modifications to the buildpkg.sh script that is >> distributed with openssh. >> >> I am sending it to

This patch adds the seatbelts which _only_ kill parent sshd procs... -RMallory (eg: when you ssh into a machine and pkgadd the new openssh, it will not kill your current (or anyone else's sshd session) onanother_note: the buildpkg.sh could use some exec_prefix functionality... to deal with ./configure --prefix= --exec_prefix=/usr *** bak/opensshd.in Fri Oct 19 13:36:24 2001 ---

I've had the wrong sshd daemon killed by "killing using alternate method" too many times. Would this cause anyone any grief? --- opensshd.in.old Sun Oct 21 16:42:02 2001 +++ opensshd.in Mon Jul 15 19:34:16 2002 @@ -3,11 +3,8 @@ # # Stripped PRNGd out of it for the time being. -AWK=/usr/bin/awk CAT=/usr/bin/cat KILL=/usr/bin/kill -PS=/usr/bin/ps -XARGS=/usr/bin/xargs

I used the latest version from here: http://www.mls-software.com/opensshd.html On my other (Windows 10) machine (on which openssh works), I have cygwin installed, but if ssh was using cygwin, I wasn't aware of it. I just ran ssh from the command prompt. Wallace Forman 913-669-4453 On Wed, Jun 29, 2016 at 4:37 PM, ?ngel Gonz?lez <keisial at gmail.com> wrote: > On 29/06/16 21:36,

https://bugzilla.mindrot.org/show_bug.cgi?id=1628 Summary: /var/run/sshd.pid file collisions... Product: Portable OpenSSH Version: 5.2p1 Platform: Other OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: unassigned-bugs at mindrot.org

Hi, We compiled and successfully installed OpenSSH 3.8.1p1 (or earlier version), but has false respond from lssrc -a command. Example error message as: openssh daemon itself - "opensshd tcpip inoperative" or other daemon - "0513-001 The System Resource Controller daemon is not active" We've installed the following filesets on several AIX servers

Hi ! I'm trying to authenticate users on a Linux Red hat AS 2.1 against a radius server. I have upgraded my OpenSSHd to : OpenSSH_4.2p1, OpenSSL 0.9.6b [engine] 9 Jul 2001 The users accounts are NOT stored locally on the sever (no accounts in /etc/passwd ). Users ssh to the box : ssh test at testserver.com passwd: test I'm usign PAM to direct the authentication request to the radius

http://www.openssh.com/faq.html#3.5 It's a documented issue with Slackware. - Ben On Thu, 12 Apr 2001, Luiz Henrique wrote: > hi, i'm trying to configure the opensshd package.. > i'm on a slack 7.1 box, but i always got the permision denied message, the auth is by password.... i've tried to change the sshd_config but it hasn't work. > I don't have pam instaled.

Dear Mr. Lindstrom, I have just installed openssh-3.4 on solaris 8 sparc with the following options below but when I try to start the openssh daemon using the supplied script I get this error message; "starting /usr/local/openssh/sbin/sshd... Killed /etc/init.d/opensshd: Error 137 starting /usr/local/openssh/sbin/sshd... bailing." Another problem encountered during installation was

Would somebody perhaps have some background on these tar files with such interesting names? To my understanding, OpenBSD=4.1 == OpenSSHD-4.6. Of course, this could just be a prank. Google knows about the mail address this (presumably) came from since about mid-2007, so it apparently has not been created just for the occasion.. Thanks in advance Jan -------------- next part -------------- An

On Wed, 29 Jun 2016, ?ngel Gonz?lez wrote: > On 29/06/16 22:57, Wallace Forman wrote: >> I used the latest version from here: >> >> http://www.mls-software.com/opensshd.html >> >> On my other (Windows 10) machine (on which openssh works), I have cygwin >> installed, but if ssh was using cygwin, I wasn't aware of it. I just ran >> ssh from the

Hello all, I was finally able to create the OpenSSH package for Solaris 8 10/01. The problem I have now is that I will still need to have entropy ready prior to openssh-3.1p1 package installation. Otherwise there is no entropy pool available (with the new servers) and key generation fails. With the previous versions of openssh, I used SUN's "makeOpenSSHPackage.ksh" script and was

I have just installed openssh on my Sun Cobalt Qube, running Linux. The shell interpreter for the rc script forces /sbin/sh. This is defined in opensshd.init.in. This shell does not exist on this implementation of Linux. I have written about this in (much more) detail at http://blogs.sun.com/roller/page/DaveLevy/20060104. NB This would seem to me to be a common problem but I havn't found

http://bugzilla.mindrot.org/show_bug.cgi?id=752 Summary: Lack of Message file and Eventlog Application Source registry entries result in event log errors Product: Portable OpenSSH Version: -current Platform: All OS/Version: Cygwin on NT/2k Status: NEW Severity: minor Priority: P2

I have a list of CLIDs prefixes that I want to use in a context. Basically, I want to do this but the list of prefix numbers is much longer. List of prefixes (556,557,557,989.....) [custom-inbound] exten => _556,1,answer exten => _556,n,playback(beep) exten => _557,1,answer exten => _557,n,playback(beep) exten => _558,1,answer exten => _558,n,playback(beep) exten =>

Hi, I downloaded setupssh-7.3p1-2.exe for Windows x64. I created private public keys and set it up accordingly. After entering the passphrase, I see authentication succeeded message but then the connection to the remote host gets closed immediately. Some of the Client output: ************************ ... Enter passphrase for key '/home/user2/.ssh/id_rsa': debug1: Authentication

(I'm not subscribed to the list, please Cc me on replies). We have configured sshd to listen on port 80 for some of our users who are behind sufficiently paranoid firewalls. However, others are now confused since they're expecting a web server on port 80. So, I created a small patch (just as proof-of-concept so far), that determines the type of client connecting. A web client will start

https://bugzilla.mindrot.org/show_bug.cgi?id=1584 Summary: umask setting in sshd Product: Portable OpenSSH Version: 5.2p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy: leo.baltus at omroep.nl

Hi. Solaris packages created by buildpkg.sh don't create privsep user or group and sshd won't start until they are created (or privsep is disabled): ## Executing postinstall script. starting /usr/local/sbin/sshd... Privilege separation user sshd does not exist /etc/init.d/opensshd: Error 255 starting /usr/local/sbin/sshd... bailing. The attached patch (against -cvs) ports the relevant