jndn

10/12/2015

08:47 AM Feature #3251: Allow encoder to use multiple signature types

We would like to use arbitrary signature schemes to compute the data packet signature. Ideally, the use of a specifi... Moreno Ambrosin

10/11/2015

04:34 AM Feature #3251: Allow encoder to use multiple signature types

For SignatureHmacWithSha256, there is an open issue #3075 to to add support since the security library was initially ... Anonymous

10/09/2015

05:10 PM Feature #3251: Allow encoder to use multiple signature types

I agree, signatures are part of the forwarding logic of NDN, and should have no other meanings. I could certainly add... Moreno Ambrosin

09:21 AM Feature #3251: Allow encoder to use multiple signature types

The idea is that the spec for the Data packet only includes fields that might need to be processed by an NDN forwarde... Anonymous

09:08 AM Feature #3251: Allow encoder to use multiple signature types

Dear Jeff, we defined our own algorithm and application-specific key management/storage. What would be useful in our ... Moreno Ambrosin

10/08/2015

02:47 PM Feature #3251: Allow encoder to use multiple signature types

To clarify, you have defined your own application-specific signature algorithm and TLV type? Do you want to send a da... Anonymous

01:45 PM Feature #3251 (Closed): Allow encoder to use multiple signature types

In https://github.com/named-data/jndn/blob/master/src/net/named_data/jndn/encoding/Tlv0_1_1WireFormat.java#L844, the ... Andrew Brown

10/01/2015

10:22 AM Bug #3228 (Closed): Name components do not compare correctly

Added Blob.compare for unsigned compare. Use it in Name.Component.compare. Anonymous

09/28/2015

12:06 PM Bug #3228 (Closed): Name components do not compare correctly

Since we are all having a great time at NDNCOMM, I thought I would rain on the parade by posting this bug. Name compo... Andrew Brown