discuss: Need disclaimer boilerplate
Subject:
Re: Need disclaimer boilerplate
From:
"David Braun" ####@####.####
Date:
15 Aug 2003 02:12:57 -0000
Message-Id: <10951-09915@sneakemail.com>
Okay, thanks for your advice. I decided to go with my own simple
wording:
Following the instructions in this HOWTO will make accessing
your data more difficult (on purpose). If you make a mistake
you may lose access to your data permanently. I take no
responsibility for any damages you may incur. Make good and
frequent backups and proceed at your own risk.
I've finished the HOWTO and put it in front of the linux-crypto list to
get some feedback. It's not yet ready for submission to the LDP but
you're welcome to take a look if you like:
http://mica.nfshost.com/HOWTO/Disk-Encryption/
David Braun
(previously Adam)
On Wed, 2003-08-13 at 22:35, David Lawyer wrote:
> On Wed, Aug 13, 2003 at 07:52:19PM -0700, Adam wrote:
> > I'm putting the finishing touches on my Disk Encryption HOWTO and will
> > soon make it available for feedback before I submit it to the LDP.
> >
> > I want to include a disclaimer section which absolves me of any
> > responsibility since it's possible through the use of encryption to lose
> > data. Can someone point me to a good boilerplate for this? I think
> > it'd be useful to put into the LDP Author Guide.
>
> Even in the long GFDL you have to write your own disclaimer, if you want
> one. If a document is provided free, I'm not sure that it needs a
> disclaimer. I doubt if there is any case law for such a situation. But
> there is case law for a similar situation where someone voluntarily goes
> to someone's aid in an emergency. If you do this, you can't be
> irresponsible. So I think that regardless of whether or not you have a
> disclaimer in your document, you need to write responsibly.
>
> For example, when I mention how to test for voltage with ones tongue, I
> warn them. So I would suggest just warning people in the doc that
> encryption can lose data. Anyway, I also put this in my license:
>
> Since this is free documentation, it should be obvious that I cannot
> be held legally responsible for any errors.
>
> But this is wrong of course. It you knowingly tried to bring harm to
> the reader, then you could be held responsible. Or if you were grossly
> negligent about writing it, even if the error was unintentional, you
> could be held accountable.
>
> David Lawyer
>
> ______________________
> http://lists.tldp.org/
