Tutul
banner
tu-tul.bsky.social
Tutul
@tu-tul.bsky.social
🏳️‍🌈
he/him

$2a$11$.R3pwaz7d2LDB6tl8tEp3.ay3IljC0MW/PWRGbY7Ubrb9Y2c.JRL.
as I recall: disk encryption could only mitigate those attack where the encryption is secure but not against knowing user manipulation (jailbreak, inside job, backdoor, etc.)

still waiting for a solution like signed disk encryption with TPM secret or stuff like that
November 4, 2025 at 7:27 PM
Yea but they explicitly put those appart from they claim. I understand why as those a well founded attack researched for a long duration and could even include production line attack to open backdoors.

First part look like written by marketing and but the second part is very nice to read
October 2, 2025 at 6:01 AM
OK with the technical details in there but the preface showing that iPhone never had a major attack is probably more the result of the heavily locked and expensive ecosystem. If the possible gain from an attack is dwarfed by the cost of developing it, it won't be tried. But nice paper still
October 2, 2025 at 5:49 AM
But we also provide an app on the server to validate the signatures and show the sealed content for easy use.
With a page detailing the how-to, the technical details, and the public certificate.

Seem to be well received by the other parties.
September 25, 2025 at 5:36 AM
And if the signature is valid but the content differs between the document and the sealed data, that mean someone edited the PDF but didnd't even try to forge the signature.

Why the big qrcode? So that tiers can verify in-house with our public key. Instead of trusting a server from middle attack
September 25, 2025 at 5:34 AM
So, in any doubt, you would need to check the content stored in the qrcode. If the content is the same as the document, and the signature is valid, then the document is legit.
If the signature isn't valid against our public key, then the document and the qrcode were forged.
September 25, 2025 at 5:32 AM
At my work we had a problem where other institutions had trouble telling if our documents where legitimate or forged by the user. I proposed a solution, that come with a big chubby qrcode, where the important (aka. Legally binding element) where store along a signature of that JSON for all to verify
September 25, 2025 at 5:30 AM
Si tu parle de rendre visible dans qqch que tu exporte/partage, cela implique que l'application qui visionne ai accès aux données des détecteurs. Ce n'est pas le cas. Faudrait avoir des demandes de permissions que les gens vont refuser en se demandant pourquoi est-ce que la biblio image en as besoin
September 24, 2025 at 1:52 PM
Wait, your dryer use gas? 🤨
I didn't know it was (still) a thing
September 18, 2025 at 5:58 AM
dammit I miss it 🥲
May 10, 2025 at 3:34 PM
For a moment, my European ass was wondering why the "stolen land" before realizing they aren't European ^^'
April 7, 2025 at 9:50 AM
BS propose pack made by user for following/blocking, you might find one that suit you.

But that is a sign that the website has grow, strangely
January 26, 2025 at 12:12 AM
Look like backpain, poor blue :-/
January 12, 2025 at 2:28 PM
Blue is way too calm about that xD
January 9, 2025 at 6:39 AM