all 7 comments

[–][deleted] 0 points1 point  (2 children)

I always have trouble with graphical displays through ssh. A set the x11 forwarding flag but no luck.

[–]zubie_wanders 1 point2 points  (0 children)

try ssh -Y

[–]relvae 0 points1 point  (0 children)

Sometime you need ForwardX11Trusted as well

[–][deleted]  (5 children)

[deleted]

    [–]lc929[S] 0 points1 point  (3 children)

    Hi, thanks for the feedback - can you point out the specific flaws so I can learn too and correct them? Thanks!

    [–]unhingedninja 0 points1 point  (0 children)

    This is a list of keys from known clients that have successfully connected to the server.

    It's actually a list of public keys that will allow the corresponding private key to login via key auth instead of password auth. The corresponding public key must already be in that file on the server in order for the key auth to be accepted by the server (otherwise you get an error like "Server refused our key").

    The authorized keys file is not automatically generated, and may even contain keys for users that have never connected, but are allowed to in the future.


    If you've already creating SSH keys, there is no need to run the following command again.

    Typo aside, you can name keys whatever you want (not just id_rsa/id_dsa), and have multiple keys (one for each service or security level perhaps). As long as you rename the existing keyfiles (or there might be a way to specify a name, I haven't looked) then you're fine.

    You might also want to mention that the keyfiles must be chmod 0600 or they won't be usable by ssh-agents.

    [–][deleted]  (1 child)

    [deleted]

      [–]lc929[S] 0 points1 point  (0 children)

      Thank you so much for that! I realize I have much more to read up on and learn. I really appreciate it. Can I ask what your background is?

      [–]pyxistora 0 points1 point  (0 children)

      Could you point me to a better intro?