SSH Key generation question
in [General Linux]
|
From: J G Miller on 20 Jun 2010 16:16 On Sun, 20 Jun 2010 12:52:56 -0700, Todd complained: > Both machines are listening. My "beef" with their calling the > workstation the server This is where you are going wrong. The workstation is a workstation and a server machine is a server machine. But in terms of software daemon services, there is an X11 server running on the workstation. > Little picture: the X11 folks are saying it is a server because it is > listening for rendering from somewhere else. Therfore it is a server. Nobody is saying that the workstation is the server. They are saying that the screen with the association X11 software running on that workstation is providing an X server. The DISPLAY environmental variable is the key to understanding which X11 server it is that you are using. If it is just :0.0, it is using the local X11 server. If it is set to this_workstation:0.0 then it using the local X11 server. If it is set to some_other_machine:0.0 then output of the X11 clients are going to the X11 server on that some_other_machine. When you execute a client program which speaks to a server you would type something like my_prog -h host_name Similarly with X11 programs you would type something like my_X11_prog -display host_name:0.0 In each case host_name is the name of the machine where the server software is running, be it a database server or an X11 server. And in either case it could be the local workstation. So as you can see, there is no difference between the conventional client / server program syntax and the X11 client /server program syntax.
From: J G Miller on 20 Jun 2010 16:21 On Sun, 20 Jun 2010 19:36:48 +0000, General Schvantzkoph wrote: > For Putty it's some equally easy way of doing it. For Windoze users, it is remarkably easy to use. See the details and a nice picture of puttygen see <http://winscp.net/eng/docs/ui_puttygen> They even get the chance to wiggle the mouse during key generation! This is for the purpose of generating some randomness.
From: Maxwell Lol on 20 Jun 2010 16:34 Todd <todd(a)invalid.com> writes: > Another follow up question: > > If I disable root to root access (no logon as root > through ssh), does that preclude a remote user > from "su" to root? No. But you can use sudo instead of giving them root password.
From: Todd on 20 Jun 2010 16:35 On 06/20/2010 01:16 PM, J G Miller wrote: > Nobody is saying that the workstation is the server. They are saying > that the screen with the association X11 software running on that > workstation is providing an X server. > > The DISPLAY environmental variable is the key to understanding which > X11 server it is that you are using. You do an excellent job of explaining it. (I am only pruning your quote as nntp.aioe.org bounces too many quoted lines.) My beef remains. Regardless of the DISPLAY variable, the workstation is responding to output from the cruncher that it requested. The workstation is not blindly listening to anything. Rather it is listen on network connection that it established. If I were to send blind rendering from another computer, the workstation would reject them as I had not established a network connect with it first. The workstation's X portion is only acting as a server in a micro sense. In a macro sense, it is acting as a client: it is responding to something it requested. By the way, you are an excellent technical writer. I admire that. I can not write two line without screwing something up. -T
From: Maxwell Lol on 20 Jun 2010 16:35
> Cygwin works fine for that purpose. You can pretty much do anything that > an ssh client can do on Linux, create a keypair, ssh into a remote > machine, do rsyncs, run CVS over ssh. Cygwin uses an identical ~/.ssh > directory and the identical ~/.ssh/config files. Putty uses a different directory, but you can install keys there as well... |