shalomail 0.2.1 → 0.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -1
- package/dist/index.mjs +27 -27
- package/dist/shalom.mjs +52 -51
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -94,7 +94,8 @@ Every command accepts `--json`, `--as <address>` to pick the mailbox, and `--api
|
|
|
94
94
|
- Your account key creates agent mailboxes and shows your plan. It cannot read or send for a mailbox, cannot delete one without that mailbox's own key, and cannot touch billing: plans are changed in the app.
|
|
95
95
|
- The keys of shalomail.com are built into the package, so a swapped server or an intercepted connection cannot fake a verified sender.
|
|
96
96
|
- Between Shalom addresses, mail is sealed end to end and the sender is verified. To other providers it goes as regular email.
|
|
97
|
-
- The encryption keys of Shalom contacts are pinned on first use
|
|
97
|
+
- The encryption keys of Shalom contacts are pinned on first use, when you send to them or receive from them. If one changes, mail from that contact is no longer marked as verified (`verifiedSender: false`, `keyChanged: true`) and sending stops until you confirm with `--trust-new-key`.
|
|
98
|
+
- Text from emails (sender, subject, body, attachment names) is printed without terminal control characters, so a message cannot change your terminal.
|
|
98
99
|
|
|
99
100
|
## Plans
|
|
100
101
|
|