URL:
<http://savannah.gnu.org/bugs/?19767>
Summary: `setauth' doesn't really work
Project: The GNU Hurd
Submitted by: tschwinge
Submitted on: Tuesday 05/01/07 at 11:42
Category: Hurd
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Reproducibility: None
Size (loc): None
Planned Release: None
Effort: 0.00
Wiki-like text discussion box:
_______________________________________________________
Details:
The only thing I was able to use it for was to provoke a system crash.
I tried to do a ``setauth -g devel'' after having created a `devel' group.
`setauth' asked me for a password -- what password does it want me to type
in?
Running a plain ``setauth'' without any command line arguments made it
iterate through all processes (I suppose), displaying either ``setauth:
[pid]: Operation not permitted'' or ``setauth: [pid]: Cannot get auth port:
(ipc/send) invalid destination port''. The latter ones are the ids of
processes that don't even exist anymore, as a comparison with ``ps -Af''
could tell me.
After that I was left with no ids:
#v+
$ ids
effective uids:
effective gids:
available uids:
available gids:
#v-
Running ``setauth -g devel'' again made the system crash. (I can't reproduce
this at the moment, however.)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?19767>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-hurd mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-hurd
