According to david dahl (mozilla engineer) window.crypto.getRandomValues is very close to landing in FF. The problem seems to be that FF mobile does not have a window.crypto object yet. So shouldnt be long I hope...
Tankred Am 27.06.2012 00:34 schrieb "Niklas" <[email protected]>: > It turned out window.crypto.getRandomValues() is a Gecko thing, and for > some odd reason my Firefox installation on OS X didn't want to deal with > it. I also found this document along with the example tips you guys gave to > be very useful: > http://gpg4browsers.recurity.com/GPG4Browsers-Developer_Documentation.pdf > > Seems like I got it playing steadily now, and although it disturbs me that > the entropy collection doesn't work in Firefox I'll get to that later. > > Thanks for the help guys, I'll definitely get good use from OpenPGP.js and > might come up with something to share soon. > > Regards, > Nik > > On 6/26/12 11:02 AM, Niklas wrote: > > I'd love to do a quick documentation, but I think getting the test cases > and the provided Chrome plugin to work as a demonstration would be good > enough. It's JavaScript after all. :-) > > The unit tests in /test/index.html call the undeclared function > window.crypto.getRandomValues() in openpgp.crypto.js (thus at least also > /test/encryption.html is broken). Not sure if the rest is important, but > the only working tab under coverage is summary. Also > jscoverage_browser_load is undefined. > > OpenPGP private key parser doesn't do proper test output ( [object > Object]), not sure if this is limited to test output or the parser does an > incorrect return. > > So yeah, I came around to more or less abandoning /test/ figuring it > couldn't help me out. The uncertainty of whether it's the lib or the test > files themselves that are broken kind of ticks me off from tinkering with > the lib. I didn't look twice at the Chrome extension that was included in > the repo after realizing that nearly all includes were wrong. > > Thanks for pushing the update and providing the link to gmail-crypt. I'll > have a look and see if I can get a grasp of it all :-) > > Regards, > Nik > > > On 6/26/12 7:54 AM, Sean Colyer wrote: > > Niklas, > > Sorry for your frustration getting started with the project. I think we > would all like for there to be more documentation, but it's just something > that hasn't been a top priority. It would be great as you learn to use the > framework if you could write even some basic documentation as an > introduction. > > Can you explain what you mean about /test being entirely broken? > > I've pushed some updates to the chrome plugin that comes with the project > that should make it load the proper js. This part of the project is one > that unfortunately doesn't get too much attention. > > If you're looking for a project that uses openpgp.js, you can check out my > chrome extension: https://github.com/seancolyer/gmail-crypt > > Hope this helps a bit. > Sean > > On Sun, Jun 24, 2012 at 9:39 AM, Niklas <[email protected]> <[email protected]>wrote: > > On 6/24/12 8:34 PM, Niklas wrote: > > the example in ./resources/ doesn't even include the js lib that it's > > supposedly demonstrating > Oh wait, it does. At the end. Outside the head tag, unlike how it's > included everywhere else. This might actually be it. > > Consider these confusing emails a manifestation of how confusing it is > for me to get started with openpgpjs. :( > > If this is all provided, scratch the previous email, and thanks! :-) > _______________________________________________ > > http://openpgpjs.org > > > > _______________________________________________ > > http://openpgpjs.org > > > > > > > _______________________________________________ > http://openpgpjs.org > > > > > _______________________________________________ > > http://openpgpjs.org > >
_______________________________________________ http://openpgpjs.org
