🚀 go-pugleaf

In article <125003@uunet.UU.NET> ebersman@uunet.UU.NET (Paul Ebersman) writes:

   I have poked a bit in the code and still cannot get gnuclient on one
   machine to talk to the gnuserv on a different machine. I am using Epoch
   3.2 and the gnuservX from uiuc.edu. I get a new buffer if I do gnuclient
   on the machine that I start the serve on. However, when I do "gnuclient
   -h hostname filename" on a different machine, I just get my prompt
   back. I do get exit status 0...

   If the server process is not running at all, I DO get the cannot connect
   message.

   What am I stupidly missing?

I wouldn't say "stupidly", since it's not the most obvious thing in
the world.  Also, I missed it myself...  :-)

This is from the man page, and I think it's what you're looking for:

    SECURITY

    Using Internet-domain sockets, a more robust form of security is
    needed that wasn't necessary with either Unix-domain sockets or
    SysV IPC.

    gnuserv performs a limited form of security at the machine level.
    By default only connections from the host where the server is
    running will be allowed. All other server connections will be
    rejected with a cryptic message (which is displayed only by
    gnudoit ). Alternatively, if the variable GNU_SECURE can be found
    in gnuserv 's environment, and it names a readable filename, then
    this file is opened and assumed to be a list of hosts, one per
    line, from which the server will allow requests. Note that a host
    may be either a internet address, or a hostname. If this file
    contains a lot of hostnames then the server may take quite a time
    to start up.

I just created a file that contains all the hosts I'm likely to use,
set GNU_SECURE to that file, and now things work fine.

--
   Steve Baumgarten             | "New York... when civilization falls apart,
   Davis Polk & Wardwell        |  remember, we were way ahead of you."
   baumgart@esquire.dpw.com     | 
   cmcl2!esquire!baumgart       |                           - David Letterman

In <BAUMGART.91Mar11081220@info7.esquire.dpw.com> baumgart@esquire.dpw.com (Steve Baumgarten) writes:

>I just created a file that contains all the hosts I'm likely to use,
>set GNU_SECURE to that file, and now things work fine.

Indeed. You are the second person to correctly point this out. It now
works. Might I suggest to that ~/.rhosts might be a reasonable default
if no security file is set?

-- 
                   Paul A. Ebersman @ UUNET Communications
                   uunet!ebersman or ebersman@uunet.uu.net
       The difference between theory and practice in practice is greater
           than the difference between theory and practice in theory.