Gustav,
>Eric Sisler wrote:
>
[more snippage]
> > 1) On the client, run ssh-keygen (use the -d switch to generate a DSA
> > key). This creates the following files in ~/.ssh
> > identity(ssh1 private key)
> > identity.pub(ssh1 public key)
> > id_dsa (ssh2 private key)
> > id_dsa.pu
Gustav,
>Because of a lack of physical space, lack of monitors and lack of
>keyboards. (I've got lots of mice laying around, but...)
Ah - I know the feeling. I've got three servers hooked up to an OmniView
mouse/keyboard/monitor switch.
>Last, but not least, it *looks* good. :-) All my Win or
Gustav Schaffter wrote:
>
> Tried to ssh from the 'client' to the 'server'. Was asked for the
> passphrase. Gave it. Was *also* asked for the login password on the
> 'server'. Gave it but login was refused.
> I.e. the DSA key was *not* used but my ordinary login password was used
> for authentifi
Just to support Gustav...
I have two linux boxes on a lan:
1) A nice Cheapo Pentium 75 with three cables: a phone, a network and a
power, it dials up and does IP forwarding for my LAN: Total cost: $60.00
2) A database server running Oracle.
Neither has monitor or keyboard or mouse... saves sap
Eric,
Because of a lack of physical space, lack of monitors and lack of
keyboards. (I've got lots of mice laying around, but...)
Last, but not least, it *looks* good. :-) All my Win oriented friends
asks me about the PC. I can answer: "Oh, Linux doesn't require any of
that. Linux runs as I want
Eric, see below.
Eric Sisler wrote:
> If you're using strictly ssh2, I *think* you'll need to use DSA
> authentication rather than RSA authentication, although the procedure is
> pretty much the same:
Correct.
> 1) On the client, run ssh-keygen (use the -d switch to generate a DSA
> key). Th
Bret,
I fully agree. I had already done the same.
Regards
Gustav
Bret Hughes wrote:
> Just to give myself a warm and fuzzy I also set the PermitRootLogin no
> option
>
> Bret
--
pgp = Pretty Good Privacy.
To get my public pgp key, send an e-mail to: [EMAIL PROTECTED]
Visit my web site at
On Fri, 08 Sep 2000, Bret Hughes wrote:
>
> Just to give myself a warm and fuzzy I also set the PermitRootLogin no
> option
>
Yep. Not a bad plan. Then you can always ssh in as a user and su to
root, as needed. :-)
John
___
Redhat-list maili
Eric Sisler wrote:
> Gustav,
>
> >Well, I wanted to replace rsh, rlogin, telnet and ftp within my small
> >home LAN. (Currently 7 PCs with two more in the pipeline.)
>
> An admirable goal. ;-) I don't have any of the r* services installed on
> any of my servers and ftp is only allowed on one an
Gustav,
>Well, I wanted to replace rsh, rlogin, telnet and ftp within my small
>home LAN. (Currently 7 PCs with two more in the pipeline.)
An admirable goal. ;-) I don't have any of the r* services installed on
any of my servers and ftp is only allowed on one and only from specific
hosts. B
Eric,
Well, I wanted to replace rsh, rlogin, telnet and ftp within my small
home LAN. (Currently 7 PCs with two more in the pipeline.)
Especially, I want to use ssh as the only way to login to my Internet
Gateway (that I'm right now configuring for use with ADSL within a month
or two). The Gatew
I echo what Eric said. You basically, install the RPM binaries and it
works. Only thing you need to do is connect once to a new host (once per
login) and say 'yes' (*not* 'y') to the prompt to store that hosts'
cert. Oh, you have to start sshd in /etc/rc.d/init.d.
If you don't have the RPM'
Gustav Schaffter <[EMAIL PROTECTED]> wrote:
>Anyone knows where I can find some basic HOW-TO or equivalent covering
>the practicals of configuring and using ssh, particularly openssh?
There isn't really much to the basic install - you'll need openssh,
openssh-server, openssh-clients and openssl
Hi,
Anyone knows where I can find some basic HOW-TO or equivalent covering
the practicals of configuring and using ssh, particularly openssh?
I have studied the man pages until my eyes bleed, but there are still
parts of the basics concepts I don't understand.
Hate to admit it, too. ;-)
Regard
14 matches
Mail list logo
