From: caszonyi@rdslink.ro
To: "Anna G. Zapata" <azapata@du.edu>
Cc: Linux-Newbie <linux-newbie@vger.kernel.org>
Subject: Re: upgrading open ssh
Date: Mon, 23 Feb 2004 23:45:05 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.53.0402232343260.1619@grinch.ro> (raw)
In-Reply-To: <HBEJLOFMLEPBMAAEFNFDMECICFAA.azapata@du.edu>
On Mon, 23 Feb 2004, Anna G. Zapata wrote:
> Hi all,
>
> I downloaded and installed the latest version of open ssh. I was running openssh-3.6.1p2-19 on a Fedora box. However,
> how do I know that the new install took and that the old open ssh has been done away with? I did the ./configure, make,
> and make install, but I think I'm missing some steps.
>
ls -l `which sshd` `which ssh`
and look at time field
they should have the date you installed them
> Thank you as always.
>
> Anna Zapata
> UTS - Network Security
> 303.871.2009
>
>
--
"A mouse is a device used to point at
the xterm you want to type in".
Kim Alm on a.s.r.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-02-23 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 21:12 upgrading open ssh Anna G. Zapata
2004-02-23 21:30 ` Armen Kaleshian
2004-02-23 22:03 ` Anna G. Zapata
2004-02-23 22:52 ` Armen Kaleshian
2004-08-19 15:13 ` ssh setup: user 'locked out' daily Eve Atley
2004-08-19 16:12 ` John Kelly
2004-08-19 18:54 ` Eve Atley
2004-09-08 5:27 ` -p option for useradd ( was Re: ssh setup: user 'locked out' daily ) Stephen Samuel
2004-12-22 15:38 ` Interpreting disk space and changing backup path Eve Atley
2004-12-22 16:28 ` Ray Olszewski
2004-12-22 20:37 ` qwms-avib
2004-02-23 21:44 ` upgrading open ssh Ray Olszewski
2004-02-23 21:45 ` caszonyi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0402232343260.1619@grinch.ro \
--to=caszonyi@rdslink.ro \
--cc=azapata@du.edu \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox