Re: problem with ssh from work to home
- From: "Russ P." <russ.paielli@xxxxxxxxx>
- Date: Sun, 19 Dec 2010 11:26:01 -0800 (PST)
On Dec 19, 7:59 am, Wolfgang Meiners <WolfgangMeiner...@xxxxxx> wrote:
Am 19.12.10 09:53, schrieb Russ P.:
I am running RHEL Linux at work and Ubuntu at home. I can ssh into
work from home but I can't ssh to home from work. When I try to ssh
into my home computer, I get no response.
I'm guessing that I need to open port 22 on my home computer or
something like that. Is that true? Can someone give me a clue about
how to do that or what else I need to do? I have Comcast cable and a
Netgear WNDR3700 router.
I think I have a dynamic IP address at home, but I've been told that
it won't change very often, so I'll be contented to just manually keep
track of it for now. However, I would like to know the best way to
figure out what it is at any given time. Thanks.
Russ P.
As far as i know, ubuntu does not install openssh-server by default. So
you will have to do this manually.
When you installed openssh-server it should be running. You should try
to connect to your ubuntu-workstation from the lan-side. If that works,
you should be sure, to have strong passworts for any account on your
workstation. From the second, where you expose your workstation to the
internet, there will be attempts to connect to it.
It might be better to have a look at
/etc/ssh/sshd_config
and disable password-authentication:
PubKeyAuthentication yes
PasswordAuthentication no
ChallengeResponseAuthentication no #may be needet to
PermitRootLogin no #if not really needet
read man 5 sshd_config for deatails and dont forget to restart sshd
after you changed sshd_config. Try to connect to your workstation with
passwort. You should not be allowed to do that with the settings above.
The next step is to forward port 22 from the wan-side of your router to
port 22 of your ubuntu-workstation. Maybe it is better not to forward
port 22 but to choose some other port for this. Have a look at your
router how to do this.
Maybe you need a dyndns-account or something like that if your
ip-address changes to often.
If you want to use PubKeyAuthentication, the next step will be to
generate a private/public keypair on your workstation at work. I would
only do this, it is really safe there. Any one who has access to your
account at your workstation at work can connect to your workstation at
home! (At least if the private key has no passphrase set).
You should run
ssh-keygen
and copy the public key to the
${HOME}/.ssh/authorized_keys
of your ubuntu-workstation at home.
If everything went well you can ssh from work to your workstation at home..
Wolfgang
Thanks for that information. It's a bit more involved than I had hoped
it would be. I'll have to decide whether it's worth the effort for
what I need it for. I don't intend to login to my home computer from
work very often. The only reason I would like to be able to do it is
in case I do extensive work from home and then forget to sync with my
work machine. I'd like to be able to sync from work. But if I just
remember to sync every morning before I leave for work, I'll never
need to login to my home computer from work. Maybe a google calendar
reminder every morning is all I need!
Russ P.
.
- Follow-Ups:
- Re: problem with ssh from work to home
- From: jdanskinner
- Re: problem with ssh from work to home
- References:
- problem with ssh from work to home
- From: Russ P.
- Re: problem with ssh from work to home
- From: Wolfgang Meiners
- problem with ssh from work to home
- Prev by Date: Re: problem with ssh from work to home
- Next by Date: Re: problem with ssh from work to home
- Previous by thread: Re: problem with ssh from work to home
- Next by thread: Re: problem with ssh from work to home
- Index(es):
Relevant Pages
|