Hi Brian and Andrew,

On Mon, Apr 15, 2019 at 08:02:46PM +0100, Brian Potkin wrote:
> On Fri 05 Apr 2019 at 16:44:31 +0100, Brian Potkin wrote:
> 
> > On Sun 10 Mar 2019 at 14:09:27 +0000, Andrew M.A. Cater wrote:
> > 
> > > Severity 911844 normal
> > 
> > It would be useful to know the reason why the severity has been reduced
> > to normal. I would have thought a confidential document should not end
> > up on a machine it was not intended for.
>

My guess would be that it's because a work environment where with
multiple departments and printers should have its network partitioned
such that this type of confidentiality breach could not occur. eg: in
a workplace where confidentiality is important, systems from different
departments can only communicate to each other through restricted
channels, and cannot even ping each other--let alone each others'
printers.

> Being accorded the courtesy of a reply is not, it seems, on the horizon.
> And one wonders why Debian is sometimes not seen as an OS responsive to
> a reasonable request.
>

Debian is people, and most of us are volunteers.  I'm guessing Andrew
is busy with work, end of scholastic year, etc.  P.S. An alarmist tone
will not motivate anyone to fix a bug faster ;-)

> Never mind. If the intention is to dissuade from questioning, the lack
> of response has made its point. The motto appears to be - it's a secret:
> don't ask!

No, that's not true...  Debian is developed in the open.  Also, our
community is substantially more responsive to bug reports than those
from other three big free distributions.  It's one of the primary
reasons I chose to work on Debian vs alternatives :-)

Personally I think this is an important bug, but not because of
confidentiality.  Eg: If there is an expensive colour printer, and a
normal monochrome one, bulk jobs shouldn't randomly be routed to the
expensive printer when they are intended for the affordable one.  It's
a problem if a 200 page report is printed on a photo printer.  Thank
you for filing it, that's an important contribution imho.

Andrew, please comment soon.

Regards,
Nicholas

Attachment: signature.asc
Description: PGP signature

Reply via email to