Bug 671269 - javaws shows wrong publisher when prompting user
Summary: javaws shows wrong publisher when prompting user
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 13
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Omair Majid
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: CVE-2011-0706
TreeView+ depends on / blocked
Reported: 2011-01-20 22:22 UTC by Ville Skyttä
Modified: 2011-03-01 16:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-03-01 16:52:21 UTC
Type: ---

Attachments (Terms of Use)

Description Ville Skyttä 2011-01-20 22:22:51 UTC
$ rpm -q java-1.6.0-openjdk
(IIRC happens also in F-14 but cannot verify that right now)

$ javaws http://portecle.sourceforge.net/webstart/portecle.jnlp

As expected, javaws prompts the user to accept the certificate this web start app is signed with because it cannot be verified (it's a self signed one), but while doing it, it shows the wrong publisher.

This app contains two jars: portecle.jar which is the main jar and signed with my key (Ville Skyttä), and bcprov.jar which is signed with my key as well as the Bouncy Castle one.  javaws should show "Publisher: Ville Skyttä" in the initial certificate acceptance prompt, but it shows "Publisher: The Legion of the Bouncy Castle".

However, "More information..." -> "Certificate Details" shows my certificate as it should.

javaws from both Oracle's and IBM's JRE's show the correct publisher in the initial acceptance prompt.

Comment 1 Tomas Hoger 2011-03-01 15:34:44 UTC
I'm being told this was part of the larger problem - see bug #677332 - and should be fixed in the latest Fedora openjdk packages.  I'm seeing correct publisher with java-1.6.0-openjdk-

Comment 2 Ville Skyttä 2011-03-01 16:05:11 UTC
I no longer have a F-13 box to test with, but the correct publisher is shown with on F-14.

Comment 3 Tomas Hoger 2011-03-01 16:52:21 UTC
Thanks, I'm making this public and closing.

Note You need to log in before you can comment on or make changes to this bug.