Skip to Content.
Sympa Menu

cacert-policy - Re: [CAcert-Policy] Policy about code signing certificate

Subject: Policy-Discussion

List archive

Re: [CAcert-Policy] Policy about code signing certificate


Chronological Thread 
  • From: Iang <iang AT iang.org>
  • To: Policy-Discussion <cacert-policy AT lists.cacert.org>
  • Subject: Re: [CAcert-Policy] Policy about code signing certificate
  • Date: Mon, 17 Dec 2007 15:59:27 +0100
  • List-archive: <https://lists.cacert.org/cgi-bin/mailman/private/cacert-policy>
  • List-id: Policy-Discussion <cacert-policy.lists.cacert.org>

Lambert.Hofstra AT ins.com
 wrote:
Let's say that we agree with that principle, and CAcert is out of the
picture.

Do we also say that the end-user also is never to be held responsible?
Or do we say that the end-user *is* to be held responsible?

Define "end user": is this
a) the owner of the CSC?
b) the person running the code?
c) someone else?


Above, I meant the NRP, the poor sod who's computer just got trashed, or worse, bank account raided.

That is, there are these parties:

a. code author
b. code distributor
c. CAcert
d. Assurer(s)
e. Browser vendor
f. end-user / NRP
g. attacker

For now. The question for the moment is to allocate the Risks, liabilities and obligations amongst that set.

Please sum the numbers to 100% :)


(all rest in your email, ok.)

iang

PS: darn it, my computer is installing an unsigned quicktime bug fix... restart required.




Archive powered by MHonArc 2.6.16.

Top of Page