Skip site navigation (1)Skip section navigation (2)
Date:      27 Jun 1996 16:31:47 -0400
From:      bill@twwells.com (T. William Wells)
To:        freebsd-questions@freebsd.org
Subject:   Re: a talkd/write improvement I made
Message-ID:  <4qur3j$qr0@twwells.com>
References:  <4qtdi8$gjd@twwells.com> <199606271226.MAA00863@jraynard.demon.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
In article <199606271226.MAA00863@jraynard.demon.co.uk>,
James Raynard  <fqueries@jraynard.demon.co.uk> wrote:
: > This means: allow steph@cyberenet.net to "talk"; forbid everyone
: > else on that machine. Allow anyone at admin.cyberenet.net to talk;
: > forbid everyone else. (It's using fnmatch(3).)

: Sounds useful.

It is. I'm the head admin for an ISP and people are constantly
annoying me about trivia. It goes from annoying to fingernail-
on-blackboard when trivia is transmitted at the half-finger typing
speed of most people. So I normally want talk off. But there are
people who have legitimate need to talk to me and who can type
fast enough to make it worthwhile, so sometimes I turn it
on....and then get more annoying talks. I've been wanting a way to
allow selective talks for a long time and when, last night, I
decided I needed a programming break, as in "I'm a programmer,
dammit, and I'd like to write the occasional program!", I decided
to do it as a short project.

: > This is all well and good, except that the write program can also
: > be an annoyance. So I modified it, too. But there's a problem.
: > While talkd runs as root and so can see anyone's .talkrc, write
: > runs as the invoking user and if that user can't see the callee's
: > .talkrc, write reverts to the default behavior, which is to allow
: > the write.
:
: How about *not* allowing the write if .talkrc exists but is
: unreadable? That way, I can make my .talkrc readable by a group that
: represents, for example, people working on the same project, and use
: it to filter them more selectively, while shutting everyone else out.

That doesn't resolve the problem. The usual problem is people
protecting their home directories. Then, I can't tell if they
have a .talkrc. Also, your suggestion isn't going to do much for
talkd....



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4qur3j$qr0>