iliasabs

5 ms·

1.
by iliasabs 10mo ago
First of all, thanks for the thoughtful comment and link. You're right that rotating every crypto algo to PQC right away might be a bit too aggressive. The actual best practice (like you said) is hybrid: layer ML-KEM/ML-DSA on top
2.
Shor's algorithm: the one quantum algo that ends RSA/ECC tomorrow(blog.ellipticc.com)
68 points by iliasabs 10mo ago|35 comments
3.
by iliasabs 10mo ago
need more API credits rn
4.
by iliasabs 10mo ago
Hi, thanks for pointing this out, code sample has been fixed (using mlkem library now, pqcrypto.kem.kyber768 was deprecated late 2022 and fully removed from PyPi in early 2023). I tried only the RSA code but not the Kyber one, lesson learne
5.
by iliasabs 10mo ago
No worries, I totally get it. The style definitely came off too polished rather than being authentic, raw. I’ll stick closer to my own voice in the future. Appreciate the advice.
6.
by iliasabs 10mo ago
Totally get the fatigue around SaaS posts. This one was to explain the differences in simple terms, polished/rewritten with AI. The CTA was optional, I’ll make it clearer next time. Thanks for the feeeback.
7.
by iliasabs 10mo ago
Fair point on the writing style, I’ll try to make it better next time. The post itself hasn’t been AI-generated but rewritten/polished with AI. Appreciate you taking the time to read it and giving feedback.
8.
by iliasabs 10mo ago
I implemented Kyber in a browser-based E2EE app and shared lessons learned. Happy to answer technical questions or clarify points from the post.
9.
Kyber vs. RSA-2048(blog.ellipticc.com)
11 points by iliasabs 10mo ago|11 comments
10.
by iliasabs 10mo ago
This seems like a solid embeddable option. Have you tried it in a real-time analytics or caching scenario yet? Curious how it behaves under heavy write loads.
11.
by iliasabs 10mo ago
Yep, that’s correct—none of the companies listed are actual clients. They were just placeholders to make the landing page look a bit more complete while we’re still early in the product’s journey. Appreciate you pointing it out—I’ll make th
12.
by iliasabs 10mo ago
Thanks for your feedback! You’re right—integrating remote storage would improve the experience. WebDAV is an option, but I’ll need to explore ways to make it work while keeping true E2EE intact. Regarding the testimonials, the companies lis
13.
by iliasabs 11mo ago
The repo is the frontend — it includes all the client-side encryption, authentication, and UI logic. It’s still a bit rough around the edges design-wise, but the core logic and crypto implementation are solid and fully functional. Some feat
14.
by iliasabs 11mo ago
Thanks a lot for the feedback — that was really helpful! I’ve just pushed an update addressing your points: commit d94969a( https://github.com/ellipticc/drive-frontend/commit/d94969a63... ) — N and G are now p
15.
by iliasabs 11mo ago
Thanks for the feedback — to clarify, only the frontend is open-sourced at the moment, sorry for any confusion. I’ve also just added an MIT License to make that explicit. The backend isn’t public yet, but we may open parts of it later.
16.
by iliasabs 11mo ago
Thanks for pointing that out! Could you elaborate on what specifically looks off about the SRP implementation? I tried to follow RFC 5054 with some minor adjustments for the frontend (using hash-wasm and fixed-length encoding to match the s
17.
by iliasabs 11mo ago
Yes, sorry — I’ve focused more on the actual logic of the dashboard rather than the landing page, which still lacks polish. Regarding the data, all your files are stored on Backblaze B2 servers (EU-central), with their data centers located
18.
by iliasabs 11mo ago
Thanks for your advice!
19.
Show HN: Ellipticc Drive – open-source cloud drive with E2E and PQ encryption(ellipticc.com)
21 points by iliasabs 11mo ago|16 comments