similar to: [Fwd: Some interesting hashes]

(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

I'm not sure I'm barking up the right tree here, but would I need to make use of groups to plot two separate datasets within ONE panel in xyplot? The desired end result is a single xy plot of two separate (but similar in values and ranges). Full code follows, xyplot code at bottom #########Determine Frequencies ##########coastal_slope #needs the maptools package to read ESRI grid

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

GoIAX, the Asterisk community's free IAX provider, is offering free US dids now. I loaded about 175 dids in and put up a very beta sign in page. Unfortunately I had to restrict the free us/canada outbound calling back down to toll-free only. There was a lot of war dialing and prank calling going on. I'm working on some stuff to hopefully curb that kind of stuff down so I can

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

Hi, I've been reading all I can on Google (and Asterisk TFOT book) looking for ideas on how to implement an automated blacklist feature. I would like to automatically blacklist a incoming number based on timestamp and count information. For example, if I get a prank call from the same number 5 times within 15 minutes, I want my dialplan to automatically blacklist this number. Should I be

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

Also, if password-based auth is not allowed, WTF would you want to log passwords? This whole idea is ugly, and smacks of a teenage-level prank attempt. I would strongly object against any such modification of the main source (though I'm sure the maintainers are sane enough to never let such a crap in). Of course the original poster is free to hack his own copy in whatever way he wants.?

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

Hello everyone, this is my first mail to the list, please forgive me if some of my questions have been asked before. I'm currently thinking about a way to implement an efficient logging method for authentication results together with client connection info on my linux boxes. My aim is to circumvent expensive and delayed mechanisms like tail()ing syslog to get to the required info and be able

http://bugzilla.mindrot.org/show_bug.cgi?id=324 ------- Additional Comments From jan.iven at cern.ch 2002-06-30 09:19 ------- Created an attachment (id=125) KRB4/KRB5/AFS with privsep ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1246 Summary: Protocol version identification errors don't log the sender IP anymore, always UNKNOWN Product: Portable OpenSSH Version: 4.4p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: sshd

Hello, in order to use "scp", the scp binary has to be in the compile-time default path on the remote host. For some users (like root), we try to avoid this since scp may be on a network file system (AFS/NFS), and we don't want to hang root's session on network outages. Would a patch to scp be acceptable in the main tree that allows to set the path to remote scp explicity,

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