From: Todd on 20 Jun 2010 17:54 On 06/20/2010 02:00 PM, J G Miller wrote: > What it all comes down to is your frame of reference. > I concure
From: Todd on 20 Jun 2010 17:55 On 06/20/2010 02:04 PM, J G Miller wrote: > On Sun, 20 Jun 2010 13:06:41 -0700, Todd wrote: > >> I am thinking that sending him his private key "out-of-band" (through >> the postal service on a CD in a password scrambled zip file) would work >> around the situation. > > It will take less time for the business client to fire up puttgen than > it will to get the CD out of the case, mount it, find the contents > in the file explorer, click on it, open the password, unzip the file > and then worry about moving the contents to an appropriate directory. > > Furthermore, does the business client really want you to have the > security of his account compromised by you holding a copy of his > private key? Good point. I don't know if he care. But, I will find out. -T
From: Todd on 20 Jun 2010 18:35 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.
From: Todd on 20 Jun 2010 18:41 On 06/20/2010 02:04 PM, David W. Hodgins wrote: > Here's an example that may help make it clearer. > > I use ssh to establish a connection to a remote computer. On > that computer, I start gkrellm. The client, gkrellm requests > a connection to the x11 server running on my machine, and uses > that connnection to send the dialog to the server, and get > keyboard and mouse input, from the server. That is an excellent way of explaining why the X11 folks choose to call the workstation x stuff a server. 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. The naming should have been chosen based on the functional outcome of the processes. Not the nitty gritty on one of the processes. Also, vncserver does the same thing. Thankfully, they choose to name things base on the functional outcome. -T
From: John Hasler on 20 Jun 2010 19:29
Todd writes: > 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. That is not part of the X11 protocol. You could go to the "cruncher", log in on the console there, start gkrellm, and tell it to display on the workstation (provided you had authentication set up appropriately). You could then log in on the console of another "cruncher" and do the same again. > Also, vncserver does the same thing. No it doesn't. > Thankfully, they choose to name things base on the functional outcome. They named things on exactly the same basis as did the X developers. -- John Hasler jhasler(a)newsguy.com Dancing Horse Hill Elmwood, WI USA |