java - Applet - Both signed and unsigned code warning message only with 1.6.0_45 -


i'm working legacy code login performed through applet (as i've commented legacy code ;d). we've been working several jre versions (1.6.0_29, 30 , 43) , have been working without problem. customer has requested use 1.6.0_45 jre version. moment, when login applet going executed, user displayed alert message shown in this link.

the jar behind applet signed certificate ca, , verification of jar gives following result:

         636 tue may 14 15:57:56 cest 2013 meta-inf/manifest.mf          702 wed may 15 09:45:38 cest 2013 meta-inf/cert.sf         4669 wed may 15 09:45:38 cest 2013 meta-inf/cert.rsa            0 tue may 14 15:57:58 cest 2013 meta-inf/            0 tue may 14 15:57:58 cest 2013 meta-inf/maven/            0 tue may 14 15:57:58 cest 2013 meta-inf/maven/folder0/            0 tue may 14 15:57:58 cest 2013 meta-inf/maven/folder0/folder1/ smk     2829 tue jul 03 14:02:34 cest 2012 meta-inf/maven/folder0/folder1/pom.xml        x.509, cn=aaa, ou=bbb, o=ccc, l=ddd, st=eee, c=en (alias)       [certificate valid 11/11/12 1:00 14/01/14 0:59]       x.509, cn=thawte code signing ca - g2, o="thawte, inc.", c=us       [certificate valid 8/02/10 1:00 8/02/20 0:59]       [keyusage extension not support code signing]       x.509, cn=thawte primary root ca, ou="(c) 2006 thawte, inc. - authorized use only", ou=certification services division, o="thawte, inc.", c=us       [certificate valid 17/11/06 1:00 31/12/20 0:59]       [keyusage extension not support code signing]       x.509, emailaddress=premium-server@thawte.com, cn=thawte premium server ca, ou=certification services division, o=thawte consulting cc, l=cape town, st=western cape, c=za       [certificate valid 1/08/96 2:00 2/01/21 0:59]  smk      120 tue may 14 15:57:58 cest 2013 meta-inf/maven/folder0/folder1/pom.properties        x.509, cn=aaa, ou=bbb, o=ccc, l=ddd, st=eee, c=en (alias)       [certificate valid 11/11/12 1:00 14/01/14 0:59]       x.509, cn=thawte code signing ca - g2, o="thawte, inc.", c=us       [certificate valid 8/02/10 1:00 8/02/20 0:59]       [keyusage extension not support code signing]       x.509, cn=thawte primary root ca, ou="(c) 2006 thawte, inc. - authorized use only", ou=certification services division, o="thawte, inc.", c=us       [certificate valid 17/11/06 1:00 31/12/20 0:59]       [keyusage extension not support code signing]       x.509, emailaddress=premium-server@thawte.com, cn=thawte premium server ca, ou=certification services division, o=thawte consulting cc, l=cape town, st=western cape, c=za       [certificate valid 1/08/96 2:00 2/01/21 0:59]             0 tue may 14 15:57:58 cest 2013 folder2/            0 tue may 14 15:57:58 cest 2013 folder2/generalrequirements/            0 tue may 14 15:57:58 cest 2013 folder2/generalrequirements/accesscontrol/            0 tue may 14 15:57:58 cest 2013 folder2/generalrequirements/accesscontrol/passwordmanagement/            0 tue may 14 15:57:58 cest 2013 folder2/generalrequirements/accesscontrol/passwordmanagement/applt/            0 tue may 14 15:57:58 cest 2013 folder2/utils/ smk     4811 tue may 14 15:57:58 cest 2013 folder2/generalrequirements/accesscontrol/passwordmanagement/applt/pwapplt.class        x.509, cn=aaa, ou=bbb, o=ccc, l=ddd, st=eee, c=en (alias)       [certificate valid 11/11/12 1:00 14/01/14 0:59]       x.509, cn=thawte code signing ca - g2, o="thawte, inc.", c=us       [certificate valid 8/02/10 1:00 8/02/20 0:59]       [keyusage extension not support code signing]       x.509, cn=thawte primary root ca, ou="(c) 2006 thawte, inc. - authorized use only", ou=certification services division, o="thawte, inc.", c=us       [certificate valid 17/11/06 1:00 31/12/20 0:59]       [keyusage extension not support code signing]       x.509, emailaddress=premium-server@thawte.com, cn=thawte premium server ca, ou=certification services division, o=thawte consulting cc, l=cape town, st=western cape, c=za       [certificate valid 1/08/96 2:00 2/01/21 0:59]  smk     2185 tue may 14 15:57:58 cest 2013 folder2/utils/mycrypter.class        x.509, cn=aaa, ou=bbb, o=ccc, l=ddd, st=eee, c=en (alias)       [certificate valid 11/11/12 1:00 14/01/14 0:59]       x.509, cn=thawte code signing ca - g2, o="thawte, inc.", c=us       [certificate valid 8/02/10 1:00 8/02/20 0:59]       [keyusage extension not support code signing]       x.509, cn=thawte primary root ca, ou="(c) 2006 thawte, inc. - authorized use only", ou=certification services division, o="thawte, inc.", c=us       [certificate valid 17/11/06 1:00 31/12/20 0:59]       [keyusage extension not support code signing]       x.509, emailaddress=premium-server@thawte.com, cn=thawte premium server ca, ou=certification services division, o=thawte consulting cc, l=cape town, st=western cape, c=za       [certificate valid 1/08/96 2:00 2/01/21 0:59]  smk      630 tue may 14 15:57:58 cest 2013 folder2/utils/mysecuritymanager.class        x.509, cn=aaa, ou=bbb, o=ccc, l=ddd, st=eee, c=en (alias)       [certificate valid 11/11/12 1:00 14/01/14 0:59]       x.509, cn=thawte code signing ca - g2, o="thawte, inc.", c=us       [certificate valid 8/02/10 1:00 8/02/20 0:59]       [keyusage extension not support code signing]       x.509, cn=thawte primary root ca, ou="(c) 2006 thawte, inc. - authorized use only", ou=certification services division, o="thawte, inc.", c=us       [certificate valid 17/11/06 1:00 31/12/20 0:59]       [keyusage extension not support code signing]       x.509, emailaddress=premium-server@thawte.com, cn=thawte premium server ca, ou=certification services division, o=thawte consulting cc, l=cape town, st=western cape, c=za       [certificate valid 1/08/96 2:00 2/01/21 0:59]     s = signature verified    m = entry listed in manifest   k = @ least 1 certificate found in keystore   = @ least 1 certificate found in identity scope  jar verified.

in this other thread i've seen manifest.mf signed, in jar not. reason why user obtain warning message? why manifest.mf file not being signed?

if above not problem, is, if jar correctly signed , significant content signed well, why jre displaying warning message indicate application contains both signed , unsigned code?

i know can use trusted-library attribute in jars manifests avoid message, know provoking displayed.

any idea? contribution appreciated.

thank in advance!


Comments

Post a Comment

Popular posts from this blog

Change php variable from jquery value using ajax (same page) -

what i'm trying this: i've php global variable $currentid , simple jquery script check if there "id" (page) in hash of url , if yes wanted give value $currentid . i've been reading lot , notice shall use ajax i'm not managing it. my code is: <script type="text/javascript"> $(document).ready(function(){ if (parent.location.hash != '' ) { var thecurrentid = parent.location.hash.split('#')[1]; $.ajax({ url: 'my.php', //current page type: 'post', data: {theid: thecurrentid }, datatype: 'json', success: function () { } }); } // code here }); </script> could me please? thank in advance. php server side language, meaning once has sent data browser, php variables , data cannot changed... however, using ajax, can send request php page , change data in dom based on result. consider th...
Read more

Pull out data related to my apps from Android Play Store and iOS App Store -

i want pull out data related apps (ratings, reviews, etc) google play store , apple app store ? how can accomplish ? i have found open source apis google mentioned not reliable. also there paid apis (e.g. appfigures) available. has idea how able pull data these play stores ?? i looking direction on how can accomplish this. can suggest ? we (appfigures) have been working on developing infrastructure give ability reviews , bunch of other data points major app stores several years :] we make available via our api though may want check out.
Read more

How can I fetch data from a web server in an android application? -

i want retrieve data web server in android application, , don't know begin. should use web services? i recommend these tutorials: connect android php , mysql , json in android , php , mysqli i used these tutorials , managed trying working without difficulty. between them describe each step in how attempting @ each stage, android application, database , web server side , has information included can process , use received information the thing add connect android php , mysql tutorial makes use of mysql_ in php deprecated. better use mysqli why included third link. the basic outline of want this: 1) in android app make request server php script using class this: import java.io.bufferedreader; import java.io.ioexception; import java.io.inputstream; import java.io.inputstreamreader; import java.io.unsupportedencodingexception; import java.util.list; import org.apache.http.httpentity; import org.apache.http.httpresponse; import org.apache.http.namevaluepair...
Read more