SSH Key generation question
in [General Linux]
|
From: Kenny McCormack on 21 Jun 2010 06:24 In article <1t53f7x79l.ln2(a)goaway.wombat.san-francisco.ca.us>, Keith Keller <kkeller-usenet(a)wombat.san-francisco.ca.us> wrote: .... >Hindenburg. Titanic. Edsel. > X windows. > >Ouch! If you have fortune installed, try > >fortune -m 'X windows' > >You may have to name the fortune database explicitly; on my Slackware >13.0 box it's in fortune2: > >fortune -m 'X windows' fortune2 > >The other fortunes are equally "loving". Heh heh - now you're getting it. As I mentioned earlier, the UHG has a pretty good chapter on X. -- (This discussion group is about C, ...) Wrong. It is only OCCASIONALLY a discussion group about C; mostly, like most "discussion" groups, it is off-topic Rorsharch [sic] revelations of the childhood traumas of the participants...
From: Maxwell Lol on 21 Jun 2010 07:34 Todd <todd(a)invalid.com> writes: > My beef remains. Regardless of the DISPLAY variable, the > workstation is responding to output from the cruncher > that it requested. The computer server initiates a connection to the workstation server. >The workstation is not blindly > listening to anything. It will accept incoming connections that are authorized. >>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. This has to do with how X11 authorizes connections. > > The workstation's X portion is only acting as a server > in a micro sense. It is acting as a server in a server sense. There is no micro/macro issue. You do not understand the process. Try running wireshark. Have you carefully examined how you initiate the X11 client?
From: Maxwell Lol on 21 Jun 2010 07:37 Todd <todd(a)invalid.com> writes: > The question arises are to who request the display variable > be set that way? Not the cruncher. Right. When you talk to a server,m you have to identify the server's IP address. The cruncher can talk to many servers. It is up to you to identify the display server. Todd, have you EVER used a printer server? A file server? In all cases, you have tyo identify the server name. The cruncher specifies the server name, and then initiates a connection to that server. Just like every other client/server example.
From: Maxwell Lol on 21 Jun 2010 07:39 Todd <todd(a)invalid.com> writes: > On 06/20/2010 01:49 PM, Maxwell Lol wrote: >> Todd<todd(a)invalid.com> writes: >> >>> I would have to point out that the workstation is the >>> one who initiate the network packet as state=new, not the >>> number cruncher. >> >> Wrong. > > Good luck with your firewall rules. Good luck with yours, as you fail to understand the concept of client/server.
From: Maxwell Lol on 21 Jun 2010 07:43
Todd <todd(a)invalid.com> writes: > My beef still holds. The cruncher is still responding > to requests from the workstation, including setting > the DISPLAY variable and asking gkrellm to fire up and > send stuff to it. You fail to understand that this is occuring iin two steps. Step 1: workstation initiates a connection to the cruncher. Step 2: cruncher initates connection to the workstation display. Both machines are servers. ONe is a computer server. One is a display server. > > The naming should have been chosen based on the functional > outcome of the processes. Which it is. |