Closed Bug 288115 Opened 20 years ago Closed 19 years ago

requires Security Device login to rad signed mail - requires manual login for security device to sign mail

Categories

(Thunderbird :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: hav, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 (ax)

I have been playing to see if we're ready to switch from NS7 to the FF/TB combo
and I find two odd - well, unexpected - things in TB related to sending signed
and encrypted email...

1. requires PW entry for security device to read SIGNED (by me) mail
(note: when reading first signed email in a session I AM prompted for PW - not
required to manually login for the security device)

2. Requires MANUAL login for security device to send SIGNED email unless have
been forced to login the security device by having already read signed or
encrypted mail

-- By "manual login" I mean that I'm NOT prompted for PW - rather, I must go
through options|advanced|manage security Devices - select the device, click the
LOGIN button and enter PW etc.

Perhaps these are related to a missing option setting (though I think I have
checked them all??) - or improper installation of my cert (Thawte - though it
seems fine once I manually login to the security device) or of the correct
Thawte CA cert (though I do see it - the correct one) so I'm not sure where else
to look -- have posted in TB Support and bugs - no responses

Reproducible: Always

Steps to Reproduce:
1. start TB and compose mail mark to sign mail with digital cert
2. send - results in error
3. go to options|advanced...|login for security device
4. send signed mail works fine
may login security device any time - above order one example

====
case 2 - reading a signed email prompts for security device login

1. open TB
2 read a signed email (in any folder)
results in prompt for secirity device -- I think this is wrong and no security
device should be required to READ email unless (maybe) the mail is encrypted 

Actual Results:  
sending signed email results in error unless have loged in secirity device
manually (will not be prompted for password)

reading signed mail prompts for PW (unless have already logged in the security
device by previous read or manually)

Expected Results:  
sending signed mail should (if required) prompt for PW

reading signed (not encrypted) mail should NOT prompt for PW
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
You need to log in before you can comment on or make changes to this bug.