Re: [mfv] publish your web server content securely
Gabx <[email protected]> Wed, 10 Dec 2025 22:45:05 +0100
| Newsgroups | alt.privacy.anon-server,alt.anonymous,alt.cypherpunks |
|---|---|
| Organization | Victor Hostile Communication Center 1312 |
| Message-ID | <[email protected]> |
Stefan Claas wrote: > merkle_metadata.json.ots 514 B > Stamped SHA256 hash: efe524acc00d18c2d45a16f4a340a2503d71d4231dbf83baa7183710caddfc0c > > merkle_metadata.json 32.1 kB > SHA256: 3ea3cc82a9eb6fba6d0688fb87ce973637098f58daf3b6f10d259954a13a90c3 > > FAILURE! > > File does not match original! You're right about the OpenTimestamps failure - I published new articles after the original timestamp and forgot to re-stamp. Each blog-sync.sh regenerates the Merkle tree, invalidating the old .ots. Just uploaded a fresh timestamp. Should verify now. The mfvc verification itself works: HTTP_PROXY=socks5h://127.0.0.1:9050 ./mfvc http://n5ry24fweklbn562o7fnyefanygtwxlgi7aevn26huuxqlsftxy5ljqd.onion VERIFICATION SUCCESSFUL - 143 files verified - Domain binding correct - Root hash: f760b22d82d595cd295a22a745b4ee50e0478a0a Thanks for catching the stale timestamp. merkle_metadata.json 32.1 kB SHA256: dba36c142881c9993d2ad3833781976deb68d663a40d707a155e459ff27ef500 Gabx -- https://yamn.virebent.art https://news.tcpreset.net http://e2mjj44t3eauxra2rmrlpn7vbd6whziypccfehlrlgnnvgr6xwp5lrad.onion/