Package: ruby-rbnacl / 5.0.0-4

Metadata

Package Version Patches format
ruby-rbnacl 5.0.0-4 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
provide_libsodium.patch | (download)

lib/rbnacl/libsodium.rb | 8 8 + 0 - 0 !
lib/rbnacl/libsodium/version.rb | 9 9 + 0 - 0 !
2 files changed, 17 insertions(+)

 provide rbnacl-libsodium

disable devel gems | (download)

Gemfile | 2 0 + 2 - 0 !
1 file changed, 2 deletions(-)

 drop dependencies on development gems


0003 Drop usage of git in gemspec.patch | (download)

rbnacl.gemspec | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 drop usage of git in gemspec


0004 Drop gem dependency on rbnacl libsodium.patch | (download)

Gemfile | 1 0 + 1 - 0 !
1 file changed, 1 deletion(-)

 drop gem dependency on rbnacl-libsodium

We depend on libsodium-dev directly in the debian package.

0005 Drop development dependency on bundler.patch | (download)

rbnacl.gemspec | 2 0 + 2 - 0 !
spec/spec_helper.rb | 1 0 + 1 - 0 !
2 files changed, 3 deletions(-)

 drop development dependency on bundler


0006 fix blake2b_state struct size.patch | (download)

lib/rbnacl/hash/blake2b.rb | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 pad blake2b_state struct declaration for libsodium 1.0.13
 libsodium 1.0.13 includes a bugfix to the alignment of the
 crypto_generichash_blake2b_state struct, which was supposed to be declared
 CRYPTO_ALIGN(64).  Non-obviously, this refers to 64 *byte* alignment, not
 64 *bit* alignment, and accordingly, initialization functions that try to
 zero out a struct will walk off the end and scribble on memory if the struct
 they're passed isn't padded out to a multiple of 64.
 .
 The size of this struct rounds up to 384 bytes (6*64).  On a 32-bit system
 (where sizeof(size_t) == 4), the declared members of the struct only add
 up to 357 bytes.  Add 27 bytes of padding to our allocated struct, so that
 we allocate enough memory for either 32-bit or 64-bit architectures.
 (Ideally we would just declare an alignment for the struct the same as we do
 in GCC, but this doesn't appear to be supported in ffi.)