Your message dated Sun, 21 Nov 2021 18:00:09 +0000 with message-id <e1mor8l-0006nh...@fasolo.debian.org> and subject line Bug#982135: fixed in bearssl 0.6+dfsg.1-1 has caused the Debian Bug report #982135, regarding ITP: bearssl -- BearSSL is an implementation of the SSL/TLS protocol (RFC 5246) written in C to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: wnpp Severity: wishlist Owner: Jan Mojzis <jan.moj...@gmail.com> * Package name : bearssl Version : 0.6 Upstream Author : Thomas Pornin <por...@bolet.org> * URL : https://bearssl.org * License : MIT Programming Lang: C Description : BearSSL is an implementation of the SSL/TLS protocol (RFC 5246) written in C BearSSL is an implementation of the SSL/TLS protocol (RFC 5246) written in C. 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 Library doesn't have compatible API with mainstream OpenSSL. And it's not intended as an OpenSSL 1-1 replacement. I'm using this software and I'm going to maintain using https://salsa.debian.org/. I need sponsor.
--- End Message ---
--- Begin Message ---Source: bearssl Source-Version: 0.6+dfsg.1-1 Done: Jan Mojžíš <jan.moj...@gmail.com> We believe that the bug you reported is fixed in the latest version of bearssl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jan Mojžíš <jan.moj...@gmail.com> (supplier of updated bearssl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 10 Oct 2021 09:47:27 +0200 Source: bearssl Binary: libbearssl-dev libbearssl0 libbearssl0-dbgsym Architecture: source i386 Version: 0.6+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Jan Mojžíš <jan.moj...@gmail.com> Changed-By: Jan Mojžíš <jan.moj...@gmail.com> Description: libbearssl-dev - BearSSL - development files libbearssl0 - BearSSL - shared libraries Closes: 982135 Changes: bearssl (0.6+dfsg.1-1) unstable; urgency=medium . * Initial release. (Closes: #982135) * dfsg version: The upstream bearssl-0.6 package contains precompiled windows-binary T0Comp.exe. The binary is not needed to compile the Debian package and affects the source package. Therefore, dfsg is a repackaged version without the T0Comp.exe binary file. Checksums-Sha1: cfc395f75430acec49cbae6e59d9bb4d20c61bfd 1799 bearssl_0.6+dfsg.1-1.dsc 649ae7137b0f14872331c05ad641eb286ba587b6 499572 bearssl_0.6+dfsg.1.orig.tar.xz c0b7d2f2f0acb3c1c15f941e2c7b6c3b0755b41b 5568 bearssl_0.6+dfsg.1-1.debian.tar.xz 563b458edf60218c46da6f81433e34af83a351a0 6273 bearssl_0.6+dfsg.1-1_i386.buildinfo 389e3f3a9d3492746f4968d9857dc49ab0df5bbe 257716 libbearssl-dev_0.6+dfsg.1-1_i386.deb 45fa8430dbd0845ddc844e8362ed091f604bf9df 481820 libbearssl0-dbgsym_0.6+dfsg.1-1_i386.deb b8d7491ad7fdd0d125b9c4ce48712dac86c72790 161912 libbearssl0_0.6+dfsg.1-1_i386.deb Checksums-Sha256: 0d0fbeba51bc7324d5c74d3d6616298bde54663bdf3381d42ffd6177d43d423c 1799 bearssl_0.6+dfsg.1-1.dsc 102a625bd8f6155260867a50c508df8d8c3f796985dd744df1a68e5cd1a79004 499572 bearssl_0.6+dfsg.1.orig.tar.xz 6e1f61bc1407083d32de432d0c56f3108f9a44e44d042fab70ea3023345cad8c 5568 bearssl_0.6+dfsg.1-1.debian.tar.xz 96c6dbdd4e4e8512f039fd26737a19b9bfe0a4a6de65f78658823726dcd0a0be 6273 bearssl_0.6+dfsg.1-1_i386.buildinfo b0c3db6df1739a95b129fe87b394fb6f85c60b003f278fbc51c5cbe74c238044 257716 libbearssl-dev_0.6+dfsg.1-1_i386.deb 09dd7c05d7a74ab8c3eb489c4c0ed07ccdfec4aaaf81ab40e88ae2901a2d6ec5 481820 libbearssl0-dbgsym_0.6+dfsg.1-1_i386.deb 457e2c0d2bcdaf37f068d59089e5d43055075c340972b6e432a9d259b788bec3 161912 libbearssl0_0.6+dfsg.1-1_i386.deb Files: 69966b528da7702a31b99e0329a6eadd 1799 libs optional bearssl_0.6+dfsg.1-1.dsc 09578e3b660ba8054ba9bba4cb480fe8 499572 libs optional bearssl_0.6+dfsg.1.orig.tar.xz 0014d27dafb50edcdaecb3f71ca92a8c 5568 libs optional bearssl_0.6+dfsg.1-1.debian.tar.xz 548ee57d863da4de5a62d6236eee3dea 6273 libs optional bearssl_0.6+dfsg.1-1_i386.buildinfo 589de18c9b02a384d7c59c29bcd55c75 257716 libdevel optional libbearssl-dev_0.6+dfsg.1-1_i386.deb 4c3e78ba729551340fc48da6c0b00a5e 481820 debug optional libbearssl0-dbgsym_0.6+dfsg.1-1_i386.deb 90441c4f71e04538218d2d64a1b15f57 161912 libs optional libbearssl0_0.6+dfsg.1-1_i386.deb -----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmFi/wkACgkQH1x6i0VW QxSYLQwAo38gZPFX6SSyzY5gYnaNXgGl+6pO5MaA+0k370QiPQYgRfGUWVZbby6q iu1pRVhV+B0DnAfuGGfc+cejL0iaocgMLka6PiIUG2OCH9dVo2sJxIzvliks9dUs aObzqp99NCxAZa0RSPKHRkwhe5IJdLDR9K2AGB6//HUvqtofyeCPXYWVLqnja8/V yT7nLR3EYWxoeSqJ6PIzPXsPMWZSlKIXe+LKYF+zx53ggZBa4NSO2P+16YGgJJ7r UZiodCL5pzFMeUjYpPogfSSM3m0w8C36LXpYReAMTa1qmypeBcufXFNmN+/JVtFr JtEJbT1CWchkXuZwLeuvFBMJ8jT0EQrWT8ncwnrJM6eWBz14oupeO6gqvgEf8F/v WWTwSbOeJBXPAP4pZ+12gg0rf4LJ2GehPDBSDH/OnJlHYYSZFN9fByXawtYTg1EH cb2vIAl4ut3ECekl1WRbqWylROg7WVva+T1Uh4zNxRP5zN+etFUdCp3iun9ZTssx cqt9+ng9 =ziPn -----END PGP SIGNATURE-----
--- End Message ---
