[gpgtools-devel] Joint OpenPGP (JS) implementation

[Alex (via GPGTools)]

(since the message was bounced (first, too many recipients, then too large) - I'm sending it again just to this list).

Hi there,

just updated the attached overview picture, added two more participants to this list (Jan (Crypto Stick) and David (DOMCrypt)) and also the GnuPG mailing list (might be of interest for someone there). Please have a look at the message thread below for details.

If we can agree on the name OpenPGP.JS/openpgpjs (analog to videojs, pdfjs, ...) we should move the documentation, tickets and sources from

https://github.com/GPGTools/openpgpjs/wiki
https://github.com/GPGTools/openpgpjs/issues

to

https://github.com/openpgpjs/openpgpjs/wiki
https://github.com/openpgpjs/openpgpjs/issues

Best regards, Alex


On 19.11.2011, at 23:04, Alex (via GPGTools) wrote:

> Hi there,
> 
> also attached the scope of our project from my point of view.
> 
> Best regards, Alex
> 
> On 19.11.2011, at 11:55, Alex (via GPGTools) wrote:
> 
>> Hi there,
>> 
>> just found GPG4Browsers[2], added the URL to our (temporary) wiki[2] and the contact to our (again temporary) mailing list.
>> 
>> It seems to be clear that there is a big demand of a single core JavaScript OpenPGP implementation and we find more and more projects and developers. Still, the next issue seems to be to agree on a name before we can setup a infrastructure. Does anyone have a strong opinion on that (we can Doodle for a name)? I would like to continue with https://github.com/openpgpjs and add everyone interested in this project as admins.
>> 
>> Best regards, Alex
>> 
>> [1] http://gpg4browsers.recurity.com/
>> [2] https://github.com/GPGTools/openpgpjs/wiki
>> 
>> On 19.11.2011, at 07:27, Ryan Sears wrote:
>> 
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA256
>>> 
>>> Hi Guys,
>>> 
>>> So I realize that we're still in the very early stages of getting
>>> everything started, but I raised an issue here:
>>> 
>>> https://github.com/GPGTools/openpgpjs/issues/9
>>> 
>>> about potentially moving to a different repo, as I feel like this is
>>> more under the GPGTools wing, and less of an independent project, with
>>> equal shares from all the developers (which is what I would like to see).
>>> 
>>> I also wonder if we wish to stick with openpgpjs? Maybe we could come up
>>> with a cooler name?
>>> 
>>> What are everyone else's thoughts on this?
>>> 
>>> Also like I said last night, I'm all finished with the signature stuffs,
>>> so now it's mostly just getting everything more polished then it already is:
>>> 
>>> http://fitblip.github.com/JSPGP-Stuffs/pubkey.html
>>> 
>>> Ryan
>>> 
>>> On 11/18/2011 11:30 AM, Alex (via GPGTools) wrote:
>>>> Thanks. Added it to the page: https://github.com/GPGTools/openpgpjs/wiki
>>>> 
>>>> On 18.11.2011, at 16:45, Lukas Pitschl | Dressy Vagabonds wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> the most complete OpenPGP implementation besides GPG I could find was an implementation in Perl.
>>>>> http://search.cpan.org/dist/Crypt-OpenPGP/
>>>>> 
>>>>> Maybe it's possible to learn a little from it and help by porting portions to Javascript.
>>>>> 
>>>>> Best,
>>>>> 
>>>>> Lukas 
>>>>> 
>>>>> Am 18.11.2011 um 12:06 schrieb Alex (via GPGTools):
>>>>> 
>>>>>> Hi there,
>>>>>> 
>>>>>>> I think it would be good to outreach to the GPG mailing list.
>>>>>> 
>>>>>> I agree, this is issue 5 ( https://github.com/GPGTools/openpgpjs/issues/5 ). If someone from our small list here could sum up our current status and plan on the wiki ( https://github.com/GPGTools/openpgpjs/wiki ), I will post to other mailing lists/google/twitter/..., ask for others to participate and link to the according wiki page for more information.
>>>>>> 
>>>>>> Best regards, Alex
>>>>>> 
>>>>>> 
>>>>>> On 18.11.2011, at 03:46, Sean Colyer wrote:
>>>>>> 
>>>>>>> I think it would be good to outreach to the GPG mailing list.  Since Tino and Bill were added to this list, do either of you have any interest in working on this development?
>>>>>>> 
>>>>>>> I still have not heard back from mete0r, unfortunately.  
>>>>>>> 
>>>>>>> I've continued to work on this from my end. I'm currently working on key generation, and seem to have most of the basics outlined... I'm having some trouble generating Key ID's that agree with the ID's generated by gpg. I believe I'm following 12.2 of RFC 4880 pretty closely, but I would love some insight if anyone has worked with this bit directly...
>>>>>>> 
>>>>>>> On Sun, Nov 13, 2011 at 5:52 AM, Alex (via GPGTools) <alex at gpgtools.org> wrote:
>>>>>>> Hi there,
>>>>>>> 
>>>>>>>> * How to proceed (e.g. which infrastructure to use)?
>>>>>>> ...
>>>>>>>> I can offer to extend our existing GPGTools infrastructure to host everything related to this project.
>>>>>>> 
>>>>>>> 
>>>>>>> just to take the next step:
>>>>>>> 
>>>>>>> * Sources: https://github.com/GPGTools/openpgpjs/
>>>>>>> * Tickets: https://github.com/GPGTools/openpgpjs/issues
>>>>>>> * Documentation: https://github.com/GPGTools/openpgpjs/wiki
>>>>>>> 
>>>>>>> Best regards, Alex
>>>>>>> 
>>>>>>> 
>>>>>>> On 08.11.2011, at 23:59, Alex (via GPGTools) wrote:
>>>>>>> 
>>>>>>>> Hi there,
>>>>>>>> 
>>>>>>>> Thank you for all your answers! I think there's a big chance for us to develop a core OpenPGP JavaScript core library. Let me try to summarize:
>>>>>>>> 
>>>>>>>> Main Objectives (partly from https://github.com/GPGTools/Mobile/wiki/Introduction):
>>>>>>>> * (Test-driven) implementation of a standard JavaScript OpenPGP implementation
>>>>>>>> * Make it clean and object orientated
>>>>>>>> * Merge existing code projects while starting from scratch creating a core library but without reinventing the wheel
>>>>>>>> * Use/integrate it in other projects
>>>>>>>> 
>>>>>>>> Current Issues:
>>>>>>>> * How to proceed (e.g. which infrastructure to use)?
>>>>>>>> * How to contact Mete0r?
>>>>>>>> * Find even more developers (e.g. via gnupg mailing lists)
>>>>>>>> * Write initial tests (use cases, workflows, example messages, expectations, ...)
>>>>>>>> * Which BigInt library to use?
>>>>>>>> * Support v3 keys?
>>>>>>>> 
>>>>>>>> Needed Infrastructure:
>>>>>>>> * Ticket system (e.g. lighthouse)
>>>>>>>> * Source versioning (e.g. github)
>>>>>>>> * Documentation (e.g. github wiki)
>>>>>>>> * Communication (e.g. mailing list)
>>>>>>>> * Continuos Testing (e.g. build bot)
>>>>>>>> 
>>>>>>>> Codebase:
>>>>>>>> * Original HaneWIN
>>>>>>>> * gmail-Crypt
>>>>>>>> * mete0r
>>>>>>>> * JSPGP
>>>>>>>> 
>>>>>>>> I can offer to extend our existing GPGTools infrastructure to host everything related to this project.
>>>>>>>> 
>>>>>>>> Best regards, Alex

--
http://gpgtools.org
http://gpgtools.org/about (Google+, Twitter, RSS)