On Thu, Sep 8, 2016 at 12:10 AM, Colin Percival
wrote:
> Hi all,
>
> Tarsnap is designed to detect if your data is modified: Archives are
> cryptographically signed, and the signatures are verified before any
> data is extracted. However, this depends on the integrity of the key:
> If someone ha
I would certainly welcome this feature.
In a different domain - I have a similar scenario. There, I solved
it by tying the hash of public key to the content that is
signed+encrypted. This way, whenever a blob is decrypted (or
verified), the pubkey-hash in the blob is compared to the hash of
t
On 09/07/16 15:19, Dennis Eriksen wrote:
> On Wed, Sep 07, 2016 at 03:10:42PM -0700, Colin Percival wrote:
>> Is anyone interested in having this functionality? It seems like too
>> obscure a use case to write code for if nobody wants it yet, but if there's
>> a demand then it's definitely doable.
On Wed, Sep 07, 2016 at 03:10:42PM -0700, Colin Percival wrote:
> Hi all,
Hi!
> Is anyone interested in having this functionality? It seems like too
> obscure a use case to write code for if nobody wants it yet, but if there's
> a demand then it's definitely doable.
As far as I am concerned, an
Hi all,
Tarsnap is designed to detect if your data is modified: Archives are
cryptographically signed, and the signatures are verified before any
data is extracted. However, this depends on the integrity of the key:
If someone has your delete and write keys, they could delete an archive
and creat
