💾 Archived View for bbs.geminispace.org › u › lufte › 12773 captured on 2024-03-21 at 21:15:39. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2024-02-05)

➡️ Next capture (2024-05-10)

🚧 View Differences

-=-=-=-=-=-=-

Comment by 🛰️ lufte

Re: "Dragonlady: Client Side encryption for Gemini"

In: s/Gemini

I just noticed that Morgan mentioned my same point in a previous comment. Ignore mine.

🛰️ lufte

2023-12-18 · 3 months ago

2 Later Comments ↓

🚀 jsreed5 · Dec 18 at 14:56:

I think this is an interesting idea. What I'm confused about is where the spec for it would live in relation to the spec for Gemini itself. I wouldn't put it in the core transfer protocol, and it doesn't fit with the gemtext spec because it's not gemtext. Are you proposing Dragonlady as a new protocol to live alongside Gemini, like Titan does?

🍵 mimas · Dec 19 at 16:25:

Interesting! Since I don't host my capsule myself, the question of the trustworthiness of a third-party server came up. I would like to see gemini offer the possibility to easily store encrypted data on a foreign server, the approach here sounds exciting.

Original Post

🌒 s/Gemini

Dragonlady: Client Side encryption for Gemini — V0.1 Following the tradition of using space themed name, we present "Dragonlady" protocol an addon to gemini to enable client side symmetrical encryption named after the infamous codename used for U2 space spy plane. TLDR This proposal would enable to have client side encryption to gemini with an addon. This is backward compatible with clients not supporting it. We are looking for feedback and we are curious to know what the gemini community...

💬 ran-ford · 11 comments · 1 like · 2023-12-18 · 3 months ago · #certificates #client_certificates #encryption #programming