Closed Bug 263761 Opened 20 years ago Closed 4 years ago

Support (virus/spam) scanning of encrypted messages (both SSL and SMIME/GPG)

Categories

(Thunderbird :: General, enhancement)

x86
All
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INACTIVE

People

(Reporter: hauser, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041008
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041008

Standard virus-filters have troubles with encrypted mail (Bug 259412).
Both for SSL protected up- and downloads with ISPs as well as if the message
body is encrypted by SMIME or GPG.

I think it is a legitimate desire of end-users to also have their encrypted
traffic scanned as well in an easy way. This means, not by hand starting the
scanner, but being supported by the MUA.

As far as my understanding goes, most scanners also have a command-line /
batchable version of their program.

Therefore, one could in the MUA configure which exe to use and the MUA would in
the decryption-process run that exe over the mail body/attachments and
subsequently wipe it again (e.g like the old pgp wipe).

Alternative architectures might reach the same effect:
- forward all mail to a listener on localhost:25 or localhost:110 that sends
them to /dev/null ?
- ...

Conclusion, mozilla should not leave its users to the mercy of what the
commercial scan software providers decide for them, but support them from inside
in achieving an optimum mail scanning security.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
if providers start to implement very inconvenient features as NAV2005 described
in Bug 259412, it might even be desirable to have such a functionality not just
for encrypted mail, but for all mail.
see also Bug 135201
see also Bug 267503
leverage this configured scanner also for the download dialog of the browser
(Bug 271881)
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
QA Contact: general
Assignee: mscott → nobody
Blocks: junktracker
Motioning for a full closed status  no comments in 6  years

I am closing this as time and change have largely made the SSL/TLS component obsolete.

What happens with encrypted message sound be refiled as a new enhancement if anyone thinks it is a valuable result. But I would have thought that the option to allow anti-virus programs to scan mails would have decrypted the message before writing it to the temp folder.

Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago4 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.