mount has its shortcomings, but I think it is stretching it to
describe the reported behavior as a "secutiry hole".

It isn't likely that this problem would be allowed either to delay
the release or to force the removal of mount from the release.
Also, assuming the shortcoming exists in all versions of mount, it
shouldn't prevent new versions of mount from migrating to testing.

Therefore I suggest that the severity of this report be downgraded.

-- 
Thomas
Hood



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to