[1174] in athena10
Re: [Debathena] #116: Hook whichlocker into command-not-found
daemon@ATHENA.MIT.EDU (Debathena Trac)
Thu Feb 19 14:16:37 2009
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: broder@mit.edu, jdreed@mit.edu, andersk@mit.edu
Date: Thu, 19 Feb 2009 19:15:46 -0000
Reply-To:
Message-ID: <052.a53f3dac9cc995c0652c7e177d9bf08a@mit.edu>
In-Reply-To: <043.8b21630aa046b9f3efeeb4d1874a80d7@mit.edu>
Content-Transfer-Encoding: 8bit
#116: Hook whichlocker into command-not-found------------------------+---------------------------------------------------
Reporter: broder | Owner:
Type: enhancement | Status: new
Priority: minor | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment(by andersk):
This has been pointed out on Zephyr, and is probably obvious anyway, but
for the record: the outland locker should not be trusted for anything
under any circumstances. A hook that runs whichlocker out of the outland
locker would be a huge security problem. Even a hook that locally copies
the whichlocker database needs to present this information very carefully
to the user to avoid potentially misleading them. Also, even if
whichlocker is moved to a more trusted locker (it’s not clear that
debathena-standard users necessarily want to trust any locker), running
something out of AFS is a performance problem; it could result in long
freezes if AFS is unavailable.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/116#comment:2>Debathena <http://debathena.mit.edu/>MIT Debian-Athena Project
