Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client · HackerPapers discussions

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — mentioned by plopilop

Thu, 11 Apr 2024 09:21:32 GMT

Related research: * Why Johnny can't encrypt (1995): https://people.eecs.berkeley.edu/~tygar/papers/Why_Johnny_Ca... * Why Johnny still can't encrypt (2006): https://cups.cs.cmu.edu/soups/2006/posters/sheng-poster_abst... * Why Johnny still, still can't encrypt (2016): https://arxiv.org/pdf/1510.08555.pdf At this point I really wonder if e-mail is the best solution for encrypted asynchronous communication. E2E systems like Signal or Whatsapp offer a very functional, intuitive way to protect your texts.

Paper and discussion history. A mention is not an endorsement.

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — mentioned by nonrandomstring

Sat, 02 Mar 2024 16:34:16 GMT

Finally a protocol layer that drags email screaming and kicking into the 21st century despite 40 years of unusable cryptography [0]? [0] (Why Johnny Still, Still Can't Encrypt) https://arxiv.org/pdf/1510.08555.pdf

Paper and discussion history. A mention is not an endorsement.

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — mentioned by webmaven

Fri, 31 Dec 2021 17:18:11 GMT

> I'm using branle (https://branle.fiatjaf.com/) as my client and you can follow me with my pubkey: 22e804d26ed16b68db5259e78449e96dab5d464c8f470bda3eb1a70467f2c793. It isn't too hard to improve upon the status quo in various ways when you just drop a key usability requirement (in this case, the need for human-memorable 'handles'). It is worth reading 'Why Johnny Can't Encrypt' (1999) [0], 'Why Johnny Still Can't Encrypt' (2011) [1], and 'Why Johnny Still, Still Can't Encrypt' (2015) [2]. [0] https://www.usenix.org/legacy/events/sec99/full_papers/whitt... [1]…

Paper and discussion history. A mention is not an endorsement.

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — mentioned by gcr

Fri, 05 Nov 2021 15:13:16 GMT

See "Why Johnny Can't Encrypt", 2005: http://people.eecs.berkeley.edu/~tygar/papers/Why_Johnny_Can... Also see "Why Johnny Still Can't Encrypt", 2015: https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.22... Also see "Why Johnny Still, Still Can't Encrypt", 2016: https://arxiv.org/abs/1510.08555

Paper and discussion history. A mention is not an endorsement.

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — mentioned by dane-pgp

Mon, 20 Jan 2020 21:32:59 GMT

As an indication of the effect that the original 1999 paper has had on security research, and its legacy, let me also mention the paper "Why Johnny Still Can’t Encrypt" [1] from 2006, and the paper "Why Johnny Still, Still Can't Encrypt" [2] from 2015. Perhaps in a few more years Johnny will finally be able to encrypt using email software that supports the emerging Autocrypt standard. [3] [1] http://cups.cs.cmu.edu/soups/2006/posters/sheng-poster_abstr... [2] https://arxiv.org/abs/1510.08555 [3] https://autocrypt.org/

Paper and discussion history. A mention is not an endorsement.

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — mentioned by jamieweb

Fri, 16 Nov 2018 19:48:58 GMT

This is a famous one from 1999 - "Why Johnny Can't Encrypt" [1] There's a couple of follow-ups too, such as "Why Johnny Still Can't Encrypt" [2], and "Why Johnny Still, Still Can't Encrypt" [3]. [1] https://people.eecs.berkeley.edu/~tygar/papers/Why_Johnny_Ca... [2] https://cups.cs.cmu.edu/soups/2006/posters/sheng-poster_abst... [3] https://arxiv.org/abs/1510.08555

Paper and discussion history. A mention is not an endorsement.

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — mentioned by afarrell

Wed, 24 May 2017 11:30:50 GMT

Put money toward an organization that will hire full-time UX designers and engineers who can make open-source encryption usable by the masses. Why Johnny Why Johnny Still, Still can't encypt [2015] https://arxiv.org/abs/1510.08555

Paper and discussion history. A mention is not an endorsement.

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — HN submission

Sat, 07 Nov 2015 15:25:55 GMT

Why Johnny Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client

259 points; 160 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — HN submission

Fri, 06 Nov 2015 09:00:07 GMT

Why Johnny Can’t Encrypt: Evaluating the Usability of a Modern PGP Client [pdf]

2 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — HN submission

Wed, 04 Nov 2015 22:17:50 GMT

Evaluating the Usability of a Modern PGP Client [pdf]

2 points; 1 discussion reply on HN. Paper and source history. A submission is not an endorsement.

Why Johnny Still, Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client — HN submission

Mon, 02 Nov 2015 12:00:21 GMT

Why Johnny Still Can't Encrypt: Evaluating the Usability of a Modern PGP Client

3 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.