bearssl 0.6+dfsg.1-3 source package in Ubuntu

Changelog

bearssl (0.6+dfsg.1-3) unstable; urgency=medium

  * d/control: add Multi-Arch: same
  * d/control: bump Standards-Version to 4.6.1, no changes
  * d/copyright: update my copyright year
  * d/libbearssl-dev.lintian-overrides remove

 -- Jan Mojžíš <email address hidden>  Fri, 08 Jul 2022 17:03:42 +0200

Upload details

Uploaded by:
Jan Mojžíš
Uploaded to:
Sid
Original maintainer:
Jan Mojžíš
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Mantic release universe misc
Lunar release universe misc

Downloads

File Size SHA-256 Checksum
bearssl_0.6+dfsg.1-3.dsc 2.0 KiB 9bd17e07fc9824b0223dcb4ba14adac17981a4d8f1d63b6655819fe8f2ed98d1
bearssl_0.6+dfsg.1.orig.tar.xz 487.9 KiB 102a625bd8f6155260867a50c508df8d8c3f796985dd744df1a68e5cd1a79004
bearssl_0.6+dfsg.1-3.debian.tar.xz 5.6 KiB 051264300dffd810e7ea08f8210d3f9f61773dcd322086c0cbd02bee8d1f73df

Available diffs

No changes file available.

Binary packages built by this source

libbearssl-dev: BearSSL - development files

 It aims at offering the following features:
 .
 Be correct and secure. In particular, insecure protocol versions and choices
 of algorithms are not supported, by design; cryptographic algorithm
 implementations are constant-time by default.
 .
 Be small, both in RAM and code footprint. For instance, a minimal server
 implementation may fit in about 20 kilobytes of compiled code
 and 25 kilobytes of RAM.
 .
 Be highly portable. BearSSL targets not only “big” operating systems like
 Linux and Windows, but also small embedded systems and even special contexts
 like bootstrap code.
 .
 Be feature-rich and extensible. SSL/TLS has many defined cipher suites and
 extensions; BearSSL should implement most of them, and allow extra algorithm
 implementations to be added afterwards, possibly from third parties.
 .
 Development files.

libbearssl0: BearSSL - shared libraries

 It aims at offering the following features:
 .
 Be correct and secure. In particular, insecure protocol versions and choices
 of algorithms are not supported, by design; cryptographic algorithm
 implementations are constant-time by default.
 .
 Be small, both in RAM and code footprint. For instance, a minimal server
 implementation may fit in about 20 kilobytes of compiled code
 and 25 kilobytes of RAM.
 .
 Be highly portable. BearSSL targets not only “big” operating systems like
 Linux and Windows, but also small embedded systems and even special contexts
 like bootstrap code.
 .
 Be feature-rich and extensible. SSL/TLS has many defined cipher suites and
 extensions; BearSSL should implement most of them, and allow extra algorithm
 implementations to be added afterwards, possibly from third parties.
 .
 Shared libraries.

libbearssl0-dbgsym: debug symbols for libbearssl0