Re: Rebuilding OpenSSH on RedHat 7.3

From: Nico Kadel-Garcia (nkadel_at_comcast.net)
Date: 03/12/04

  • Next message: Fabio C.: "Pseudo-terminal will not be allocated because stdin is not a terminal." 
    Date: Fri, 12 Mar 2004 08:54:03 -0500

    "Darren Tucker" <dtucker@dodgy.net.au> wrote in message
    news:c2r5aq$h9q$1@gate.dodgy.net.au...
    > In article <c2r41m$phb$1@news2.symantec.com>, Grant <gpg86@hotmail.com>
    wrote:
    > >I've fixed it :) Apparently the "make install" target doesn't replace
    sshd
    > >with the newly built binary. Manually replacing it did the trick :)
    >
    > It does, but by default OpenSSH puts its binaries in /usr/local/{bin,sbin}
    > and most vendors (including Redhat) put their binaries in /usr/(bin,sbin}.

    Uh-oh. If he compiled for --prefix=/usr/local (the default) and did a "make
    install" and installed one binary in /usr/sbin/sshd (where RedHat puts the
    binaries), he can wind up with a world of hurt later as the SSH binaries (in
    /usr/bin, etc.) wind up confusing things with the binaries in
    /usr/local/bin, depending on how his PATH is set.

    Grant? If you've got to update an RPM installed package, please actually
    update the SRPM and build from that. It's not that hard to do, and it does a
    bunch of things like flushing away your old binaries and documentation and
    replacing them with the new stuff that you'll find useful down the road.
    Also, the default location of your sshd_config files and private keys is
    different under RedHat (in /etc/ssh/sshd_config) than it is under the
    default OpenSSH installation. (/etc/sshd_config, I think?) So you may wind
    up with some real configuration surprises if you're not careful. And the
    "make install" in the tarbal doesn't set up init scripts for you, or know
    enough to restart the daemon with the new sshd binary.

  • Next message: Fabio C.: "Pseudo-terminal will not be allocated because stdin is not a terminal."

    Relevant Pages

    • Re: installing mod_ssl on Fedora Core 4 -- complaining about httpd =?UTF-8?B?PQ==?= 2.0.
      ... just used the standard httpd binaries, which would have enabled me to ... Rather than giving you a stock Fedora server to play with, they stuff with some frankenpackages. ... Then, once that package is nuked from high orbit, I'd compile a list of all the little packages that make up that php frankenpackage, then I'd run ... After they're gone, I'd just run "yum install", which should now pull in the standard Fedora version of these packages. ...
      (comp.os.linux.misc)
    • Re: Number of downloads
      ... The bloat situation is not quite as bad as it may appear. ... initial setup script it asks if you want a full install (meaning ... But even that bloat is due to the many large binaries. ... want even the binaries from emacs, perl, python, vi, etc. it gets MUCH ...
      (comp.os.minix)
    • Re: Printing: printcap vs. interface scripts
      ... As far as I know, the lpstat or lp command that you invoke, will eventually ... In the 507 MP that added CUPS, if you install CUPS yet another layer of ... front ends that invoke either the CUPS or SYSV binaries, ... where the SYSV binaries are either the binaries for the lpsched system or the ...
      (comp.unix.sco.misc)
    • Re: RFC: 5.3 Migration Guide
      ... Existing 4.x binaries will continue working ... need to be linked to either C++ or pthreads libraries, ... recompile or update to the new version and reinstall some old libraries ... application to the new version or install new ones you have to ...
      (freebsd-current)
    • Re: Apply service pack to cluster
      ... Service packs are cluster-aware during the install. ... it updates local binaries only. ...
      (microsoft.public.sqlserver.setup)