[ANN] node-ostatus 0.1 released.

9 views
Skip to first unread message

Laurent Eschenauer

unread,
Mar 6, 2011, 10:47:06 AM3/6/11
to ostatus...@googlegroups.com, federated-...@googlegroups.com
Hi everyone,

Just letting you know that I've hacked an OStatus library and command line tools for NodeJS. It is *almost* complete. I'm missing the magic envelope signatures due to a gap in the crypto library of node. I'll try to fix this in the coming days. 


If you are already a node hacker: npm install ostatus

This is a very early version and there is a lot more work to be done to tighten the interop and support edge cases, I'll keep on actively improving it when time permits. It is also a good basis for experimenting with new concept (like testing ideas for SWAT1-Privacy support). If you play with it, please share your feedback/issues/ideas !

I'm also working on a lightweight social web server (federating over OStatus using this library). I'll let you know when I pass SWAT0 with it !

Cheers,

Laurent

James Walker

unread,
Mar 6, 2011, 12:18:27 PM3/6/11
to ostatus...@googlegroups.com, Laurent Eschenauer, federated-...@googlegroups.com
Hey Laurent, I've been following node-ostatus for a while on github.
Congrats on the initial release!!

Let me know if you need/want any help... I'll be checking out the
salmon implementation soon.

Nice work!

James

--
James Walker :: http://walkah.net/

Laurent Eschenauer

unread,
Mar 6, 2011, 3:13:03 PM3/6/11
to James Walker, ostatus...@googlegroups.com, federated-...@googlegroups.com
Let me know if you need/want any help... I'll be checking out the
salmon implementation soon.

Thanks James,

So far, so good. Early testing of interop with status.net is successful. It may be tougher with salmon signatures, and I won't hesitate to ping you if I get into troubles.

My problem at the moment is not protocol related: node.js has a basic crypto library that only supports RSA using PEM encoded keys. It is just a wrapper of openssl and there is no way to do something like PKCS#1 with modulus/exponent as input. I'm now exploring two alternatives :

- Use a javascript only crypto library
- Wrap an existing C/C++ lib for use in node.js (never done that, it may be fun but time consuming)

I'll ping the list when I have salmon interop working.

Cheers,

Laurent

Melvin Carvalho

unread,
Mar 6, 2011, 3:16:14 PM3/6/11
to ostatus...@googlegroups.com
On 6 March 2011 21:13, Laurent Eschenauer <lau...@eschenauer.be> wrote:
>> Let me know if you need/want any help... I'll be checking out the
>> salmon implementation soon.
>
> Thanks James,
> So far, so good. Early testing of interop with status.net is successful. It
> may be tougher with salmon signatures, and I won't hesitate to ping you if I
> get into troubles.
> My problem at the moment is not protocol related: node.js has a basic crypto
> library that only supports RSA using PEM encoded keys. It is just a wrapper
> of openssl and there is no way to do something like PKCS#1 with
> modulus/exponent as input. I'm now exploring two alternatives :
> - Use a javascript only crypto library

You may want to look at this, there quite a bit of .js crypto in there:

https://github.com/digitalbazaar/forge/blob/master/README

Reply all
Reply to author
Forward
0 new messages