Closed Bug 286234 Opened 19 years ago Closed 19 years ago

No successful ldaps-connection by sublevel-CA signed server-certificates

Categories

(Thunderbird :: Address Book, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: adresseverbummelt, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

Thunderbird does not connect correctly to a LDAP-Server with SSL when the
server-certificte is signed by a sublevel CA, while root-CA-cert is installed in
TB's certfificate repository, althought the whole CA-chain was sended by the
ldaps-server.

The same CA-certificate-chain ending up in mentioned server-cert works fine as
expected with "openssl s_server -HTTP ..." and Firefox with root-CA only
certificate installed at client-side.

Ethereal shows, that TB-client rejected the transmitted certificate(s): "Alert
(Level: Fatal, Description: Bad Certificate)"



Reproducible: Always

Steps to Reproduce:
1. Create multi-levelk CA hierarchy:
1.1. Create self-signed root-CA certificate
1.2. Create sublevel CA, signed by root-CA in step 1.
1.3. Create server-certificate signed by sublevel-CA in step 2.
4. Installing this certificate(s) for/in slapd
5. Installing the root-CA certificate in Thunderbird's CA-repository
6. Do a serach with either addressbook or auto-comletion-feature with newly
created messages

Actual Results:  
After searching with addressbook nothing happens, until i close thunderbird
entirerly. On exit TB remarks, that a secure connection does not finished
successfully

Auto-completionion says, that it cannot connect to the LDAp-Server in appearing
drop-down-list

Expected Results:  
Doing ldap-lookups...

You can mail me for additional information, e.g. the used certificates
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.