I have same problem with Safari 4.0.1 an updated Java (don;t have the problem with 4.0 and previous version of Java
For some reason the UnaMesa certificate (which point to the Thawte root cert) is not being trsuted as signed? Anyone find a solution? I can trust it when opening but will ask again every-time On Jun 17, 7:35 am, Andrew Lister <lis...@post.queensu.ca> wrote: > Aha - same for me. I didn't try unchecking that box. Thanks, > > Andrew > > On Jun 17, 5:33 am, Jeremy Ruston <jeremy.rus...@gmail.com> wrote: > > > > > I'm running Safari Version 4.0 (5530.17) on Mac OS X 10.5.7, with the > > new Java update just applying itself this morning. > > > The permissions dialogue that Safari displays with the applet first > > loads has changed it's appearance from the earlier release, but seems > > to work fine for me if I click "Run". It's only if I try to check the > > "always trust content from this publisher" checkbox that I run into > > the errors you describe. I'll investigate further, but relieved to > > find work around. > > > Cheers > > > Jerm > > > On Tue, Jun 16, 2009 at 8:22 PM, Andrew Lister<lis...@post.queensu.ca> > > wrote: > > > > I've been using TW on Safari 4, but after today's Java update it will > > > no longer save. Here's what I get: > > > > "Warning - Security: The application's digital signaturre cannot be > > > verified. Do you want to run the application? Name: TiddlySaver. > > > Publisher: UnaMesa Association. From: file://" > > > > Then check "always trust content from this publisher" and "run", which > > > brings up a second window: > > > > "The publisher cannot be verified from a trusted source. Code will be > > > treated as unsigned" > > > > Then it lists a bunch of code, starting with > > > java.lang.IndexOutOfBoundsException. After that it won't save. I > > > tried this on a fresh, empty TW and the same thing happens. > > > > Actually, I'm not 100% sure this problem started today, with the Java > > > update, as I also just recently updated to Safari 4, and can't be sure > > > I saved my TW on 4 prior to the update. I think I did, but I'm not > > > sure. If others haven't had any problem with Safari 4, then it must > > > be a problem with the Java update, since I've never seen this problem > > > before. > > > > So, back to Firefox for me, I guess, which is a bit disappointing, > > > because Safari 4 seemed really fast. > > > -- > > Jeremy Ruston > > mailto:jer...@osmosoft.comhttp://www.tiddlywiki.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
