OCTADE

@octade@soc.octade.net

(Owner soc.octade.net) (5&2)()()

Director of the International Department of Civil Disobedience.

For thoughtful response to thoughtful inquiry contact my email. Don't send me private direct messages on the Fediverse. If you have a general question ask it in a public timeline. I block users who send me annoying private messages about things that should be asked in a public timeline.

I sometimes post links to items I find curious, interesting, or of research and study value. This does not necessarily mean that I agree with the linked matter. Don't assume.

NAME : Raze
ACADEMIA.EDU
ABOUT
LINKS

SLOGAN : Speak not with words. Speak with work product.

PRONOMS : | | | | | |





LINKS

Cryptography project site
Publications
ORCID
[Netnews] Find me on in alt.flashback, alt.crossover, alt.rhubarb.
Git Repositories
Keyoxide1
Keyoxide2
BlueSky
HackerNews
Internet Archive

2 ★ 3 ↺

[?]OCTADE ยป 🌐
@octade@soc.octade.net

PHP Automatic Cryptographic Signature And Website Generator

[demo] https://files.octade.net/

I drafted a prototype for a PHP server application that automatically hashes and signs files and presents visitors with verification archives containing digital signatures for offline verification. The site allows readers to view, download, hash, and verify signatures of files. Since I occasionally like to publish puzzles and bits of cryptology, I just had to make this to scratch the old itch.

The neat thing about this design is that the current version has zero JavaScript. It uses CSS3 hacks with anchors and URL probing to emulate JavaScript and AJAX functionalities for modal dialogs to present server-side JSON data as HTML text.

When I upload files or documents to the server, the interface automatically presents them to the user in a grid. So now all I have to do is upload files and documents and the server generates the site.

The reader can then click buttons to hash, sign, view, verify, and download files.

GnuPG and OpenSSL Signatures are generated automatically on user demand. The site visitors can download these signatures and the public keys to verify files.

What should I add / change in the application and its interface?

What accessibility components might be warranted?

Should the application parse and present EXIF data, or is that too much?

@cryptography@soc.octade.net

    History