SSH Key generation question
in [General Linux]
|
From: Todd on 20 Jun 2010 03:38 On 06/19/2010 08:20 PM, John Hasler wrote: > Todd writes: >> The computer crunching the numbers (called the server by CUPS, Samba, >> DHCP, NAMED, yada, yada, yada) is actually called the "client". > > No. A program having something it wants displayed by the server is > called a "client". There can be many clients on many computers (one or > more per computer) including but not limited to the computer the server > is running on (a server is a program, not a computer). > >> And by common convention, it is backwards. > > No. You just don't understand the convention. > >> And, and, by referring to it as backward, you remove the "state of >> confusion" from so very many victims of the play on words. > > No. You add to it. Oh no, I do understand it. It is backwards. Okay. Lets call the computer with the data displayed on it the "lil guy" and the one doing the number crunching the "big guy". The big guy is listening for unsolicited requests. The lil' guy makes the unsolicited requests. What displays on the lil guys screen is always as a result of what it solicited from the big guy by its mouse movements and keystrokes. The lil guy is not listening for unsolicited input from any other computer. Everything it displays is as a result of what was solicited from the big guy. That makes the lil guy the client and the big guy the server. If the lil guy was displaying unsolicited input, then you would have a point. Think of it this way, if you were writing an iptables rules, which computer's input would get? -m state --state NEW,ESTABLISHED (Hint: the lil guy) and which would get? --state RELATED,ESTABLISHED (Hint: the big guy) Again, that makes the lil guy the client and the big guy the server. If you do not realize that the X11 folks reversed the convention, you are never going to figure out what went wrong in your firewall rules. So, rather than telling people they just don't understand the convention and X11 folks actually have it correct, just tell them that the X11 folks for whatever reason have reversed the convention. Doing otherwise only causes unnecessary confusion. My guess is that the X11 folks did it years ago to enforce some kind of mind set on the developers. And, that they have stuck to their guns ever since. -T
From: J G Miller on 20 Jun 2010 08:53 On Sat, 19 Jun 2010 18:44:48 -0700, Todd wrote: > X11 is an interesting play on words. Not it is not. It adheres to what is the convention of client > The computer crunching the numbers (called the server by CUPS > Samba, DHCP, NAMED, yada, yada, yada) is actually called the "client". No the daemon providing these services is called the "server" so that the client programs lp, dhclient, nslookup have something to connect to and provide the user with a result. > The computer displaying the result, which is commonly referred to as the > client by everyone else doing such thing No the daemon which provides the service by crunching numbers in order that images can by display on physical hardware is called the "server" so that the client programs xterm, metacity, firefox have something to connect to and provide the user with a a result. If you fail to follow this simple logic and call the X11 server computer the client, does that mean you regard the xterm and firefox as running as programs on a server? No, of course you do not.
From: J G Miller on 20 Jun 2010 08:54 On Sat, 19 Jun 2010 22:16:48 -0700, Todd wrote: > But if that is the way the X11 folks want to phrase it, it is okay with > me. Just as long as I know what they are up to so I can adjust for > their quirks in speech. What an insulting remark to people who know, understand and use the correct terminology.
From: J G Miller on 20 Jun 2010 09:00 On Sat, 19 Jun 2010 22:31:36 -0700, Todd wrote: > If I create his keys for him on my server You do NOT create the keys for him on your server. He creates his own keys on his own machine, and if it is running Windoze, he uses puttygen which comes as part of the PuTTY package. <http://www.chiark.greenend.org.UK/~sgtatham/putty/> The simple instructions for using Puttygen to create a pair of keys, which even a Windoze user should be able to follow, are at <http://the.earth.LI/~sgtatham/putty/0.60/htmldoc/Chapter8.html#pubkey-puttygen>
From: Kenny McCormack on 20 Jun 2010 09:06
In article <87r5k2s837.fsf(a)thumper.dhh.gt.org>, John Hasler <jhasler(a)newsguy.com> wrote: >Todd writes: >> The computer crunching the numbers (called the server by CUPS, Samba, >> DHCP, NAMED, yada, yada, yada) is actually called the "client". > >No. A program having something it wants displayed by the server is >called a "client". There can be many clients on many computers (one or >more per computer) including but not limited to the computer the server >is running on (a server is a program, not a computer). You people are completely wrong in your thinking. Not in what you post, mind you - we all understand how they defined and how that terminology works "inside the box" - but you are wrong in acting like it is some kind of moral failing to not lovingly embrace X's terminology. I.e., to not realize that it is "backwards" vis a vie the rest of the world. But again I say, there's nothing wrong with it - it is just "different". -- Just for a change of pace, this sig is *not* an obscure reference to comp.lang.c... |