Closed Bug 265350 Opened 20 years ago Closed 19 years ago

signText pops up a dialog when given the 'auto' argument

Categories

(Core Graveyard :: Security: UI, defect)

Other Branch
x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bill, Assigned: KaiE)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 I noticed a comment in the code that said it was decided to always behave as if 'ask' were given. I really would rather not write a C++ component; our project is written in JavaScript (http://p2pmud.com/). You can already execute programs from mozilla (which of course could be used to accomplish the same thing, albeit a lot more slowly). Why not allow the use of 'auto' under the same restrictions as the use of nsIProcess? The reason I marked this as 'major' is that our project is a peer-to-peer game written in Mozilla and we were planning on using digital signatures to provide some safety from spoofing attacks. Reproducible: Always Steps to Reproduce: 1. crypto.signText('text', 'auto) Actual Results: dialog pops up Expected Results: no dialog or maybe a dialog pop-up only the first time. the path to the code in question is: mozilla/security/manager/ssl/src/nsCrypto.cpp
Product: PSM → Core
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
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.