Tag Info

New answers tagged

0

You are correct in that it is an intractable problem very similar to the why DRM can never be provably secure. You can make it very difficult for a user to forge the log but ultimately the application will need to have the key needed to digitally sign log messages. If the key exists on the client computer it can be removed from the client computer. The ...


0

I would use an externally provided service (Splunk on Cloud, Papertrail - there are others but i have used these ones) to ensure reasonable integrity. Or use your own, separated from the service (based on a commercial solution or, for instance, ELK) The confidentiality part is more tricky. For the Splunk case, if you have a pre-defined list of users, you ...


5

I am kinda confused about what you are trying to achieve with this rather complicated and error-prone protocol. If I understand your idea correctly, you are basically just moving the problem of integrity onto the communications with the "hash server". If someone was able to MITM both Alice's and Bob's in- and outbound traffic, they could mess with Alice's ...


2

Your developers are correct in that any changes to the repository will be reflected by a new commit. Previous commits cannot be modified without all developers being notified of a serious conflict when updating from the remote repository. That said, it would be trivial for an attacker to add a new commit to the repository that would automatically be ...



Top 50 recent answers are included