Javaws is giving different error messages the jar file signed by damaged certificates

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P2
    • 6
    • Affects Version/s: 6
    • Component/s: deploy
    • b27
    • generic
    • generic

      The negative certificate tests are giving different error messages...

      To reproduce this bug, please launch the test applications given below...
       
      Following tests are supposed to give "Java Web Start - Download Error" with the message "Could not verify signing in resource..." since the jar file got signed using a damaged certificate, but it gives "Unexpected Error" with the message "Unable to load resource <jar file>"

      http://cheran.india.sun.com:8080/JAWSTestsNew/cerificate/damaged_signed_test.jnlp
      http://cheran.india.sun.com:8080/JAWSTestsNew/cerificate/damaged_signed_test_2.jnlp

      Please see attached damaged_signed_trace.txt for more details

      These following 2 tests should give "Download Error" with the message "Found Unsigned Entry in the resource <jar file>", but it gives "Security Error" which is different from 1.5.0.
      http://cheran.india.sun.com:8080/JAWSTestsNew/certificate/jar_after_signed_test.jnlp
      http://cheran.india.sun.com:8080/JAWSTestsNew/certificate/jnlp_signed_neg.jnlp

      Please see attached jar_after_signed_trace.txt for more details

      Build Details: (Nightly Build Feb 16)
      java version "1.6.0"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-b99)
      Java HotSpot(TM) Client VM (build 20050211120755.et151817.baseline, mixed mode, sharing)

      ###@###.### 2005-2-18 19:54:26 GMT

            Assignee:
            Thomas Ng (Inactive)
            Reporter:
            Elancheran Subramanian (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: