On Sep 11, Daniel Jacobowitz [EMAIL PROTECTED] wrote:
This is obviously wrong, ttys must have 620 permissions (or 600 if you
don't want people talk(1)ing to you, but I think the default should be
to allow it).
For ttys owned by a shell that's true, but it's set up by login(1), not
On Sep 10, Tom Lees [EMAIL PROTECTED] wrote:
Terminal devices [1] root.tty 0666
This is obviously wrong, ttys must have 620 permissions (or 600 if you
don't want people talk(1)ing to you, but I think the default should be
to allow it).
It's a huge security hole because
On Sun, Sep 10, 2000 at 09:56:30PM +0200, Marco d'Itri wrote:
On Sep 10, Tom Lees [EMAIL PROTECTED] wrote:
Terminal devices [1]root.tty 0666
This is obviously wrong, ttys must have 620 permissions (or 600 if you
don't want people talk(1)ing to you, but I
On Sep 11, Tom Lees [EMAIL PROTECTED] wrote:
This is obviously wrong, ttys must have 620 permissions (or 600 if you
don't want people talk(1)ing to you, but I think the default should be
to allow it).
For ttys owned by a shell that's true, but it's set up by login(1), not
MAKEDEV (or
On Mon, Sep 11, 2000 at 01:18:02PM +0200, Marco d'Itri wrote:
On Sep 11, Tom Lees [EMAIL PROTECTED] wrote:
This is obviously wrong, ttys must have 620 permissions (or 600 if you
don't want people talk(1)ing to you, but I think the default should be
to allow it).
For ttys owned by a
Hi there. I'm the current Debian devfsd maintainer. As you may or may not
know, the current devfsd package parses the /sbin/MAKEDEV script in its build
procedure to generate a standard list of permissions for devices (one of the
main functions of devfsd is to control the permissions of the
6 matches
Mail list logo
