Prev: Enforcing policies
Next: X Window System on Samsung n210 (Intel GMA 3150)
From: Chris Bannister on 20 Apr 2010 06:30
On Mon, Apr 19, 2010 at 11:17:12PM +0200, Merciadri Luca wrote:
> Russ Allbery wrote:

Ummm, unless I'm missing something I don't see *any* post by Russ in
this thread.

Ahh! I see from your original post you *also* posted to
debian-devel. Normally, the only reason to cross-post is
for announcements.

http://linux.sgms-centre.com/misc/netiquette.php#xpost

--
Chris.
======


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100420113129.GB18101(a)fischer
From: Chris Bannister on 20 Apr 2010 08:50
On Tue, Apr 20, 2010 at 02:27:39PM +0200, Merciadri Luca wrote:
> Johannes Wiedersich wrote:
> > Merciadri Luca wrote:
> > > Johannes Wiedersich wrote:
> > >> Why would an
> > >> honest soul ever allow information to be read, but not printed?
> > >>
> > > To maintain honesty? An honest soul (i.e. me, here) has to send some
> > > data to some dishonest person.
> >
> > The problem is: either you give data to some dishonest person or you
> > don't give that data to some dishonest person. Tertium non datur.
> Yes, but there are some nuances. Let's take my example: how would you
> have done this? You need to transmit the document, but the receivers are
> sufficiently dishonest to print it and to claim they are the authors.

To be honest that is not a question for debian-user. Maybe you should
ask a lawyer.

P.S. Please trim your posts.

--
Chris.
======


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100420135341.GA18881(a)fischer
From: Monique Y. Mudama on 21 Apr 2010 15:40
On Wed, Apr 21 at 15:04, Stefan Monnier penned:
>
> Now think about the other route: the one based on the law instead of
> technology: the legal document can simply describe what she's
> allowed to do, and that will automatically cover all imaginable ways
> to circumvent any technological means you could imagine. And if she
> does break the contract, you can sue her. Don't know about you, but
> to me, it sounds a lot more useful.

Except that most technical people would probably rather hammer a nail
through their forehead than go through the pain of suing someone and
dealing with the legal system, the paper work, the time involved ...

So looking for a technical solution, even one that requires an
enormous amount of development time, makes sense. Maybe the
development time is actually a bonus, if you're interested in that
sort of tinkering already.

All of that being said - this entire thread is really a question of
security, and security is a process and an approach, not an end result.
There is no such thing as a 100% secure system that is also useful, in
the same way that there is no such thing as a 100% secure PDF that is
also useful. So the real goal is to make the document "secure enough"
for one's purposes, while also making the document "usable enough" for
those purposes. I think there have been a lot of good ideas on this
thread for managing that trade-off.

--
monique


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100421193947.GO30298(a)mail.bounceswoosh.org
 | 
Pages: 1
Prev: Enforcing policies
Next: X Window System on Samsung n210 (Intel GMA 3150)