EmailPK

Security and privacy

email encryption

SHOW HN2014

53points
37comments
#605of 2,272 in 2014
Top 27%of 2014 by points

How HN took it

DebatedReal support and real criticism

7 positive, 6 neutral or asking, 1 mixed, 6 critical, out of 20 comments about the project. Thread score +0.14.

Idea: 2 for, 4 againstPrivacy: 1 for, 1 againstExecution: 1 for, 0 againstDocs: 0 for, 1 againstDesign: 1 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Embedding ECC keys in the address is clever and easy to share

    From 1 comment
    • This is a great idea, I hadn't thought of embedding ECC keys in the address itself. That makes them very easy to share, and backwards-compatible. I think this has great…
      StavrosK on HN
  • Important privacy idea

    From 1 comment
    • Nice. Email privacy is very important. I commend you on making something that protects people's privacy. Good job :)
      ellisonf9 on HN

Objections

  • Only works with email hosts that support plus-style aliases

    From 1 comment
    • only works with hosts that support aliases and I doubt that's many. nice idea though!
      hnha on HN
  • Recipient must have used the tool first to get a public key

    From 2 comments
    • Eh what I meant was that I should be able to send a message to any persons email. Using this app requires that the user has used it first.
      tomjen3 on HN
    • Indeed. Unfortunately, that's fundamentally the way public-key crypto works. If you do try to send a message to an email with no public key, it will prompt you to send an invite…
      diafygi on HN
  • Passphrase compromise is unrecoverable; no revocation

    From 1 comment
    • How can I generate a private key, though? (EDIT: Never mind, you just type a passphrase when you send an email. You can send me messages at…
      StavrosK on HN
  • Client-side encryption in webapps is unsafe

    From 1 comment
    • Actually this would not be great. It's kind of an unsolved problem. There is no way to do it safely.
      lawnchair_larry on HN

Requests

  • Prefill from address via URL parameters

    From 1 comment
    • This is cool! One suggestion: I currently can't bookmark a URL that just contains my email with public key in the querystring, because the app complains that some parameters are…
      lectrick on HN
  • Add a standard mailto link option

    From 1 comment
    • Could you add a “standard” mailto: link? I’m not using any of the popular webmail providers, but this looks really nice otherwise :)
      claudius on HN
  • Option to send unsigned messages

    From 1 comment
    • The only problem I'm having is that it's requesting my passphrase even though I paste my full email address (with my key embedded). I assume it's for signing? It would be very…
      StavrosK on HN

Questions

  • Why is it marked not for real secrets

    From 1 comment
    • "NOTE: THIS IS A PROOF OF CONCEPT. DO NOT USE FOR REAL SECRETS" Other than being a proof of concept, what is the real problem on using this for "real secrets?" Are there plans to…
      Fastidious on HN
  • Are Gmail-stored messages encrypted

    From 1 comment

Alternatives named

  • myLock by the same maker, for throwaway encryption

    From 1 comment
    • For throwaway/anonymous encryption, check out my other project: https://github.com/diafygi/myLock
      diafygi on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/8188042)