Re: selinux/ssh -- basic question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Sun, Mar 22, 2020 at 5:43 PM Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote:
On 2020-03-23 04:19, bruce wrote:
> do I have to have a local user on my local linux as "bob".. pretty sure I don't! but I'm not sure where the local ssh key should be placed, to allow me to ssh into the remote using the key. Also, how doe this process work when accessing the remote from other local servers.. I'm assuming, I have to copy the key/files to any box I want to access the remote VM from.

I use ssh-copy-id for this.  And, no, you don't need a user "bob" on the local machine. 

Below the local machine is "meimei" and the remote is "frk".  My user on the local machine has run the
"ssh-keygen" command so that user has a public/priviate key-pair.

[egreshko@meimei ~]$ ssh-copy-id bob@frk
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/home/egreshko/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
bob@frk's password:

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh 'bob@frk'"
and check to make sure that only the key(s) you wanted were added.

[egreshko@meimei ~]$ ssh bob@frk
[bob@frk ~]$ ls
[bob@frk ~]$ ls -a
.  ..  .bash_logout  .bash_profile  .bashrc  .mozilla  .ssh
[bob@frk ~]$ ll .ssh
total 4
-rw-------. 1 bob bob 409 Mar 23 05:42 authorized_keys
[bob@frk ~]$


All done.


Hi Ed, et al

In your example, exactly what is the
  [egreshko@meimei ~]$ ssh-copy-id bob@frk copying??

is the cmd copying the  public key for meimei to the bob/.ssh dir/path

and does the
    ssh bob@frk
log  in as the actual 'bob' user, with the bob pub/private key??

thanks



--
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux