67. pepsi-stage-secure-link¶

Hold a message that could not be encrypted, and mail out the link.

67.1. Role¶

pepsi-stage-secure-link is the far end of [stage-encrypt] ON_NO_KEY = secure-link. When encryption is required and the recipient publishes no usable key, pepsi-stage-encrypt routes the message here rather than sending it in the clear or bouncing it; the same route serves ON_OVERSIZE = secure-link and a recipient whose key lookup keeps failing in the DNS while the domain’s mail servers answer (A key lookup that fails in the DNS).

The stage takes the message off the wire entirely. It seals the message under a freshly generated PIN, stores only the ciphertext in pepsi.secure_message, injects a notification mail that carries the link, and then deletes the queue row. By default it also injects a second mail that carries the PIN to the sender, who passes it on out of band. Advancing the row would send the cleartext to a recipient who must not receive cleartext. Instead, the notification carries the message on: it takes the ordinary outbound path from [pepsi-secure-link] NOTIFY_STAGE. Reference: pepsi-stage-secure-link(1).

A message with several keyless recipients produces one stored message per recipient, each with its own token, PIN and ciphertext.

67.2. Configuration¶

The [stage-<name>] section carries only PROGRAM; everything else is in the global [pepsi-secure-link] section, which is deliberately out of reach of the per-address override layer. See The secure-link fallback portal for the whole feature, and pepsi.conf(5) for the options.

67.3. Failure¶

Everything that can fail happens before the queue row is deleted, and nothing that fails ever sends the message on — a message that reached this stage is one the operator said must not go out unprotected. If the [pepsi-secure-link] section lacks BASE_URL, PEPPER or NOTIFY_STAGE, the worker refuses to start. A fault of this host (a template, the PIN command, the database) is retried until the stage’s MAX_LIFETIME; then the message is bounced through the stage’s BOUNCE_STAGE, or failed if there is none. A null-sender message is failed at once, since there is nobody to give the PIN to. Each recipient’s stored copy and its notifications are committed together, and the link token is derived from the queue row, so a retried pass never stores or announces a recipient twice.

67.4. Security¶

The PIN is never stored and the pepsi role this stage runs as cannot read a stored ciphertext back. The threat model states these claims under the stored-message asset and the database thief (Assets, Somebody holding a copy of the database); “The secure-link portal” in Security model describes the mechanisms. Both notifications carry a recipient-bound Pepsi-Origin stamp, so a notification that comes back in to a gated mailbox on this deployment is not held for payment.

Logo

Pepsi 0.1.2

Languages

  • English
  • Deutsch
  • français

Navigation

Contents

  • 1. Introduction
  • 2. Design principles
  • 3. Getting started on a cheap VPS
  • 4. Installation
  • 5. Debian packages
  • 6. The Wizard
  • 7. Configuration
  • 8. Operating Pepsi
  • 9. Using Pepsi: a guide for users
  • 10. Troubleshooting
  • 11. Supported Features
  • 12. SMTP Protocol Extensions
  • 13. Key management
  • 14. The secure-link fallback portal
  • 15. Client interoperability
  • 16. Threat model
  • 17. Security model
  • 18. Dependencies
  • 19. Microsoft Exchange as a gateway
  • 20. Mail client extensions
  • 21. Mailing lists
  • 22. Archives
  • 23. The GNU Mailman 3 REST API
  • 24. The administrative API
  • 25. The administration console
  • 26. Architecture
  • 27. The message state
  • 28. Extending the Pipeline
  • 29. Test Suite
  • 30. Benchmark Suite
  • 31. Performance
  • 32. pepsi-ingress
  • 33. pepsi-dispatch
  • 34. pepsi-httpd
  • 35. pepsi-stage-arc
  • 36. pepsi-stage-srs
  • 37. pepsi-stage-encrypt
  • 38. pepsi-stage-decrypt
  • 39. pepsi-stage-dkim-sign
  • 40. pepsi-stage-bounce
  • 41. pepsi-stage-aliases
  • 42. pepsi-stage-relay-to-internet
  • 43. pepsi-stage-relay-to-smarthost
  • 44. pepsi-stage-relay-to-maildir
  • 45. pepsi-stage-dot-forward
  • 46. pepsi-stage-relay-to-lmtp
  • 47. pepsi-stage-discard
  • 48. pepsi-stage-anti-spam
  • 49. pepsi-stage-auto-pay
  • 50. pepsi-stage-check-whitelist
  • 51. pepsi-stage-auto-whitelist
  • 52. pepsi-stage-autocrypt-learn
  • 53. pepsi-stage-reencrypt
  • 54. pepsi-stage-detect-language
  • 55. pepsi-detect-language
  • 56. pepsi-stage-block-language
  • 57. pepsi-stage-vacation
  • 58. pepsi-stage-secretary
  • 59. pepsi-stage-edit-settings
  • 60. pepsi-stage-if
  • 61. pepsi-stage-milter
  • 62. pepsi-stage-quarantine
  • 63. pepsi-stage-route
  • 64. pepsi-stage-vks-confirm
  • 65. pepsi-stage-dmarc-report
  • 66. pepsi-stage-defang
  • 67. pepsi-stage-secure-link
    • 67.1. Role
    • 67.2. Configuration
    • 67.3. Failure
    • 67.4. Security
  • 68. pepsi-setup
  • 69. pepsi-queue
  • 70. pepsi-status
  • 71. pepsi-reputation
  • 72. pepsi-greylist
  • 73. pepsi-dkim
  • 74. pepsi-sendmail
  • 75. pepsi-whitelist
  • 76. pepsi-keys
  • 77. pepsi-keydisc
  • 78. pepsi-settings
  • 79. pepsi-list
  • 80. pepsi-archive
  • 81. pepsi-stage-list
  • 82. pepsi-stage-list-post
  • 83. pepsi-stage-list-deliver
  • 84. pepsi-stage-list-command
  • 85. pepsi-stage-list-bounce
  • 86. pepsi-tlsrpt
  • 87. pepsi-secure-link
  • 88. pepsi-failure-bouncer
  • 89. pepsi-quota
  • 90. pepsi-helper-token-refresh
  • 91. pepsi-telemetry
  • 92. pepsi-telemetry-client
  • 93. pepsi-config
  • 94. Feature stability
  • 95. Manual pages
  • 96. Vulnerabilities in E-mail implementations
  • 97. RFC Index
  • 98. Bibliography

Related Topics

  • Documentation overview
    • Previous: 66. pepsi-stage-defang
    • Next: 68. pepsi-setup

Quick search

©2026, GNUnet e.V.. | Powered by Sphinx 9.1.0 & Alabaster 0.7.16 | Page source