Can Johnny build a protocol? Co-ordinating developer and user intentions for privacy-enhanced secure messaging protocols

@inproceedings{Ermoshina2017CanJB,
  title={Can Johnny build a protocol? Co-ordinating developer and user intentions for privacy-enhanced secure messaging protocols},
  author={Ksenia Ermoshina and H. Halpin and F. Musiani},
  year={2017}
}
As secure messaging protocols face increasingly widespread deployment, differences between what developers “believe” about user needs and the actual needs of real-existing users could have an impact on the design of future technologies. In the domain of secure messaging, the sometimes subtle choices made by protocol designers tend to elude the understanding of users, including high-risk activists. We’ll overview some common protocol design questions facing developers of secure messaging… Expand
9 Citations
Mesh Messaging in Large-scale Protests: Breaking Bridgefy
  • PDF
Hackers vs. Testers: A Comparison of Software Vulnerability Discovery Processes
  • 42
  • PDF
Security Standardisation Research

References

SHOWING 1-10 OF 22 REFERENCES
You are Not Your Developer, Either: A Research Agenda for Usable Security and Privacy Research Beyond End Users
  • 57
  • PDF
Why Johnny Can't Encrypt: A Usability Evaluation of PGP 5.0
  • 1,225
  • PDF
SoK: Secure Messaging
  • 138
  • PDF
A user study of off-the-record messaging
  • 31
  • PDF
How Secure is TextSecure?
  • 59
  • PDF
Off-the-record communication, or, why not to use PGP
  • 283
  • PDF
Secure off-the-record messaging
  • 54
  • PDF
Helping Johnny 2.0 to encrypt his Facebook conversations
  • 55
  • PDF
...
1
2
3
...