[tahoe-lafs-trac-stream] [tahoe-lafs] #1874: Non-Repudiation Not covered in Integrity

[tahoe-lafs]

#1874: Non-Repudiation Not covered in Integrity
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  Narendiran
  calltodsi              |     Status:  closed
         Type:  defect   |  Milestone:  eventually
     Priority:  major    |    Version:  1.9.2
    Component:  code-    |   Keywords:  https security integrity
  frontend-cli           |  confidentiality
   Resolution:           |
  duplicate              |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Replying to [comment:4 calltodsi]:
 > Do You mean that non-repudiability is not the security properties of
 LAFS? And is it not covered in LAFS?

 That's right. Are you sure you're not confusing it with another property?
 Nonrepudiability is normally relevant only for things like contract
 signing, where a party wants to make a binding commitment that can be
 verified by anyone who has their public key. I don't think I've seen any
 storage system that provides it -- although of course you can store signed
 documents in Tahoe-LAFS.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1874#comment:5>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage