[ 17:20 bapt  ]

• 477665 security/bearssl/Makefile
• 477665 security/bearssl/distinfo
• 477665 security/bearssl/pkg-plist

Update to 0.6

[ 15:24 bapt  ]

• 450903 security/bearssl/Makefile
• 450903 security/bearssl/distinfo
• 450903 security/bearssl/pkg-plist

Update to 0.5 [1]

While here: port related changes:
- Respect PREFIX
- Build a real shared library (with SONAME)

PR:		222483 [1]
Submitted by:	takefu@airport.fm [1]

[ 19:26 feld  ]

• 438115 security/bearssl/Makefile
• 438115 security/bearssl/distinfo
• 438115 security/bearssl/pkg-plist

security/bearssl: Update to 0.4

Now requires GCC. The Clang build is not functional as it fails to link.
The cause is under investigation.

[ 20:14 feld  ]

• 431029 security/bearssl/Makefile
• 431029 security/bearssl/distinfo

security/bearssl: Update to 0.2

Changelog:	https://bearssl.org/changelog.html

[ 15:55 feld  ]

• 425235 security/Makefile
• 425235 security/bearssl
• 425235 security/bearssl/Makefile
• 425235 security/bearssl/distinfo
• 425235 security/bearssl/pkg-descr
• 425235 security/bearssl/pkg-plist

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.

WWW: https://bearssl.org/