Espen Vestre <espen@*do-not-spam-me*.vestre.net> wrote:
| Marcus Breiing <firstname.lastname@example.org> writes:
| > However, I don't like to use a TCP socket for interaction, because
| > that would tear down the wall between unix-level users, which,
| > security-wise, could make me lose sleep.
| Sure. I've used two different amendments for that. The first solution
| was to simply use a password file for the repl daemon. Now I use a
| different approach: The daemon generates a cookie (large integer)
| every now and then and writes this to file that's only readable by
| its owner. A little shell script connects to the daemon (which listens
| to localhost only) and feeds it its cookie.
A simpler/related approach is to use "detachtty" and put its
Unix-domain socket underneath a directory only you can access.
Then only you can "attachtty" to it...
Rob Warnock <email@example.com>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607