281819 - Handling the qcStatement extension of a certificate

Status: RESOLVED EXPIRED

(Core Graveyard :: Security: UI, enhancement)

Description

[Varga Viktor]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0

It was supposed to post a previously reported bug here too.
https://bugzilla.mozilla.org/show_bug.cgi?id=277797

This certificate has an extension setted to critical, and this extension was
recommended by the EU, so it will be more popular.

Please check the mentioned bug report to find out more info.

Reproducible: Always

Steps to Reproduce:
Please, read the mentioned bug report, and you will know it the whole sotry.

Actual Results:  
The certificate can't be imported because the extension is not handled yet.

Expected Results:  
Handle this type of certificate, because this will be popular in the EU, because
the regulations are recommending them.

Comment 1

[Gervase Markham [:gerv]]

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/

Comment 2

[Gervase Markham [:gerv]]

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.

Comment 3

[Varga Viktor]

The qCStatement is not needed to be critical.

It is a hard option to implement, because nobody can give a correct value for mailing or a web site, i think this extension should be recommended NOT CRITICAL.

The bug is closable, because I think this extension is a phylosophical extension, and has only function like AS IS lines in an EULA.

The solution, is to change the certificate profile and mark this extension NOT CRITICAL.