emboss/krypt — comment on commit 2e76487ccdeb6a6ae184fe2d8d552f5c98d33998
File:  line 0
By emboss:

I had to change the specs that set a value's tag to 14 (b9bf34598c7b3c3d40a15a385692dffe331ea58c). When the tag is set to 14, the internal codec will change, too, so from then on values are interpreted as raw byte strings. I think that's the only thing we can do at that point.

All specs are running through now with krypt-core at b131faf8d3b2f1c1f0ba7d056915fb887a7e8154 except for these:

- EndOfContents/Null: No error is raised when setting the value to '1'
I think that this is OK with our latest discussion about lazy construction, no? So no error should be raised?

- Integer/Enumerated: As expected, the bignum specs

- ObjectId: Illegal octet specs. I created an issue for them. (https://github.com/emboss/krypt-core/issues/28)

Now let's get that far with krypt-core-jruby :)