[guardian-dev] Otr parsing 'q' parameter failed (Java)

Fri Sep 13 21:06:05 EDT 2013

On 09/13/2013 01:46 PM, Mohamed Akram Tabka wrote:
> 
> On 13/09/13 15:16, Hans-Christoph Steiner wrote:
> 
>> Hey Mohamed,
> 
>> Have you seen the code for doing this in KeySync (formerly
> otrfileconverter)?
>>  its python, but we definitely have that part working.  While in the
> long run,
>> I think its good to have multiple implementations of things, there is
>> currently no OTR key syncing app that works completely.  KeySync is
> the by far
>> the furthest along from what I've seen.
> 
>> Parsing the DSA keys is just the starting point.  There are many annoying
>> technical details in each OTR data format which make a otherwise properly
>> converted key not work at all, things like how each app associates a
> DSA key
>> with an account.
> 
>> So I think it would be a lot more valuable at this point if we can
> collaborate
>> in figuring out all of the details of the process in KeySync, then once we
>> have a fully working implementation, it'll be much easier to write the
> Java
>> version of it.  We're committed to making Windows and Mac OS X KeySync
> apps,
>> plus its already packaged for Debian/Ubuntu/etc.  It can also be installed
>> using the python "pip+virtualenv" process on any platform.  Making an RPM
>> package for Fedora/etc. should be pretty easy to do also.
> 
>> .hc
> 
>> On 09/05/2013 07:28 AM, Mohamed Akram Tabka wrote:
>>> Hello,
>>> I'm working on an Otr key importer and when trying to import an otr key
>>> with Jitsi format and converting it into Pidgin format by parsing p, q,g
>>> x and y parameters I get always an empty q paramter .
>>>
>>>
>>> Am asking how can I get this parameter , does anyone have an idea ? I'm
>>> using Java security library.
>>>
>>>  this is an example
>>> p:
>>>
> #455d402251fb593d8d58fabfc5f5ba30f6cb9b556cd7813b801d346ff26660b76b9950a5a49f9fe8047b1022c24fbba9d7feb7c61bf83b57e7c6a8a6150f04fb83f6d3c51ec3023554135a169132f675f3ae2b61d72aeff22203199dd14801c7#
>>> --------------
>>>  q:  ##
>>> --------------
>>>  g:
>>>
> #5159578ebad4594fe67107108180b449167123e84c281613b7cf09328cc8a6e13c167a8b547c8d28e0a3ae1e2bb3a675916ea37f0bfa213562f1fb627a01243bcca4f1bea8519089a883dfe15ae59f06928b665e807b552564014c3bfecf492a#
>>> --------------
>>>  y:
>>>
> #15e344a8d86367a12afe184bfa1f957376ff9d5c009e8664a471f3552de077f4ea510f18b934cd54ba84f104633992fad924e372fdad01306525a272c9481942db538b35efce324ebc55338ab91ee4f9ef7e53b344ddb158fe77cee90bb9cc5acea7e3cbd4a9e37234c03e34471185e5843e354b06f1e5cf9b62c7d2698489a3#
>>>  x:  #****************************************#
>>>
>>> All bests,
>>>
> 
> Hi Hans,
> 
> I have seen the code of keysync, but its python, as you said, and I'm
> using java sucurity tools and otr4j .
> Anyway, I managed to load the Q parameter for an imported key. but I
> still not understand why the old version only works for a new generated
> key and not for an imported one.
>  
> Also, I want to notice that this work is for an application that builds
> OTR keys with a live Linux distribution and not for a Keysync-like . and
> it will be very interesting if I can help to make from KeySync an
> efficient and reliable tool.

We've also been discussing a TAILS-based live distro that is only for key
management.  We're planning on making it based of an OpenPGP key, then
generating subkeys for use in PGP/MIME, SSH, OTR, etc.  I'd love to hear more
about what you are working on.

We've been documenting our plan here:
https://dev.guardianproject.info/projects/psst/wiki/CleanRoom

> I will try to send you a patch to fix some bugs that I found them
> before. they was about converting to Jitsi and about the module that
> writes the OTR file formats, if I still remember.

That would be great, any info would be helpful.  Patches are even better :-D.

> I honestly don't  have a great idea about Gibberbot and other IM clients
> and if KeySync works properly for them. If there is any other thing in
> which I can contribute please let me know.

We've done testing mostly with syncing between Gibberbot/ChatSecure and
Pidgin, so that probably works the best.

.hc

-- 
PGP fingerprint: 5E61 C878 0F86 295C E17D  8677 9F0F E587 374B BE81

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 939 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mayfirst.org/pipermail/guardian-dev/attachments/20130913/a565ed25/attachment.pgp>