| browser.toml |
|
906 |
- |
| browser_displayVarious.js |
Test that a reply to a multipart/alternative message with two
encrypted parts doesn't leak the secret plaintext from the second
part.
|
3880 |
- |
| browser_encryptedRemoteContentFromFile.js |
An S/MIME enveloped message whose decrypted body carries a remote image must
hard-block that content with no "load remote content" override, whether the
message is viewed in a folder or opened from a file.
|
4435 |
- |
| browser_encryptedUriCleanup.js |
When an encrypted message is displayed, its URI is remembered by
gEncryptedURIService (used by the remote-content policy). That entry is
forgotten again when navigating away, which involves re-deriving the
message's necko URL. If the message can no longer be resolved (e.g. its
account has been removed), the cleanup must still remove the remembered entry
and must not throw and break the display of the next message (bug 2052976).
Two complementary checks: one on the cleanup itself (the entries are gone),
and one on the user-visible symptom (the next message still displays).
|
6288 |
- |
| browser_nestedSMimeSigs.js |
Test that a message containing two nested S/MIME signatures shows
the contents of the inner signed message.
|
1547 |
- |
| browser_remoteContent.js |
Remote content must stay hard-blocked for S/MIME encrypted messages, which do
not enforce integrity protection (bug 1994709, invariant #5) -- unlike
integrity-protected OpenPGP mail, an S/MIME encrypted message never gets the
remote-content override.
The test message (data/alice.remoteimage.env.eml) is an S/MIME enveloped HTML
message with a remote <img> inside the encrypted body; it is generated by
NSS's tests/smime/smime.sh and copied here by
mailnews/test/data/smime/local-gen.sh.
The message is viewed in a real folder (not opened from file) so it is
registered with the encrypted-URI service exactly as in normal use.
|
5441 |
- |
| browser_smimeSignedPartDispatch.js |
Ensure S/MIME messages that contain a multipart/signed part render
correctly, no matter at which position in the MIME tree the signed part
is found. The handler is picked from the protocol parameter of the part,
so this must work on the first stream, without a reload.
|
3794 |
- |
| data |
|
|
- |