Re: 2nd attempt: OSX/SSH Authentication Problem

From: James Hankins (jghankins_at_mac.com)
Date: 02/16/04

  • Next message: Greg Wooledge: "Re: UsersDeny except root@myserver"
    Date: Sun, 15 Feb 2004 19:18:44 -0500
    To: Byron Sonne <blsonne@rogers.com>
    
    

    Well,

    I replaced my SSHD file from backup (keeping the the /usr/bin/ssh for
    the client which previously was locking the system up periodically).
    It's working with the old SSHD at present. So at least I'm not dead in
    the water. I would like to figure this out however as it seems this
    should be doable. Obviously this is some type of compilation issue as
    the original installed binary is working but mine is not. I've tried
    the simpler no options other than path (which of course I need) to no
    avail. It must be some type of tweak that is necessary at compile
    time. (I'm using the new config from my install with the old sshd
    binary by the way)

    Regards,

    Jim

    On Feb 15, 2004, at 3:10 PM, Byron Sonne wrote:

    > Greetings,
    >
    > OK, this probably won't help you much, but the sshd_config on my
    > OpenBSD box is the same as yours. Therefore I would surmise that the
    > problem isn't in the config file.
    >
    > I've never passed options when compiling ssh, I've always just
    > accepted the defaults (i.e. ./configure, make, make install). Mind you
    > I've never tried building ssh on a Mac box, so perhaps the options you
    > mentioned are required. Try it without the various options and see if
    > that helps... and if you fix it, please let the list know... my wife
    > has an OSX box upstairs and if I ever bung it up I'd like to know how
    > to fix it! ;)
    >
    > I don't know if the 'lsof'
    > (ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/) utility comes with
    > OSX; if not, get it as it is very handy stuff! Get the original sshd
    > running and use lsof to determine what files/ports/sockets it has open
    > ('lsof | grep sshd' ought to work; capture this info to a file). Then
    > get the incorrectly functioning sshd running and do the same thing
    > with lsof as you did before. Now compare the two and look for
    > differences. This might help point you in the direction of some
    > problems.
    >
    > As always, check your paths and permissions too.
    >
    > Regards,
    > Byron
    >
    >
    > --
    >
    > For Good, return Good. For Evil, return Justice.
    >


  • Next message: Greg Wooledge: "Re: UsersDeny except root@myserver"

    Relevant Pages

    • sshd dead but subsys locked
      ... sshd dead but subsys locked ... It stands after a re-boot. ... I tried to delete the sshd file on /var/lock/subsys/, ...
      (comp.os.linux.misc)
    • trouble with OpenSSH_3.4p1
      ... Ok..this is a linux box running kernel 2.4.18 with a few grsecurity mods ..none that include the option for users to not open sockets ... I have installed: sshd version OpenSSH_3.4p1 ... Notice that the pid is owned by sshd, but an lsof of the file indicates that that the open files are owned by root.. ...
      (comp.security.ssh)
    • trouble with OpenSSH_3.4p1
      ... Ok..this is a linux box running kernel 2.4.18 with a few grsecurity mods ..none that include the option for users to not open sockets ... I have installed: sshd version OpenSSH_3.4p1 ... Notice that the pid is owned by sshd, but an lsof of the file indicates that that the open files are owned by root.. ...
      (comp.security.ssh)
    • Re: trouble with OpenSSH_3.4p1..btt
      ... > I restarted sshd after the install.. ... > Notice that the pid is owned by sshd, but an lsof of the file indicates ... > that that the open files are owned by root.. ... > a friend that has done exactly what I did, and his lsof of the pid shows ...
      (comp.security.ssh)
    • Re: trouble with OpenSSH_3.4p1..btt
      ... > I restarted sshd after the install.. ... > Notice that the pid is owned by sshd, but an lsof of the file indicates ... > that that the open files are owned by root.. ... > a friend that has done exactly what I did, and his lsof of the pid shows ...
      (comp.security.ssh)