-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reference Browser Integration for Stateless DANE #17
Comments
Would this work for mobile? Or is that more work? |
Anywhere. It's especially useful for mobile since unlike hnsd, it doesn't need to stay connected all the time. |
Awesome. Any ideas how long it would take to convert your "demo" into a working android browser (as there isn't any yet) |
Idk about a browser, but with the stateless dane lib, it should be possible to build an external app (VPN-like proxy). |
That sounds awesome. |
Kudos. This will be very valuable for Lume and HNS (and means I don't need to solve this myself 🙃) |
HELL YEAH WOOOOO |
Congrats and amazing initiative to see - looking forward to it for MASQ Browser |
What have you built previously?
A bunch of Handshake-specific tools and services, listed at https://htools.work
All projects are open source: https://github.com/htools-org
What will you be building? Why is that a valuable open source contribution to Handshake?
Stateless DANE is proposal that enables light clients to use minimal resources and can verify TLS trustlessly for any Handshake site without relying on the Handshake network all the time.
The goal here is to use the stateless dane library and integrate it with a browser: as a proof of concept, as a code demo to share with other browsers, and as a reference for alt-implementations.
Rough Roadmap:
To be clear, this is a reference, not a commitment to maintain a brand new browser, keeping it updated with security patches, etc.
Similar works:
What are completion criteria?
When will this be completed?
A bit hard to estimate, but once the stateless dane library is complete, ~4 weeks. Maybe a bit more based on the amount of work needed.
What is your contact information?
@rithvikvibhu
rithvikvibhu @ gmail . com
The text was updated successfully, but these errors were encountered: