they won't create the subdirectory either. Since the SUBST targets try
to change to WRKSRC first, they fail. This is seen with meta packages
depending on Freetype2 when using X11_TYPE=native.
py-bcrypt is a Python wrapper of OpenBSD's Blowfish password hashing code, as
described in "A Future-Adaptable Password Scheme" by Niels Provos and David
Mazieres.
This system hashes passwords using a version of Bruce Schneier's Blowfish block
cipher with modifications designed to raise the cost of off-line password
cracking and frustrate fast hardware implementation. The computation cost of the
algorithm is parametised, so it can be increased as computers get faster. The
intent is to make a compromise of a password database less likely to result in
an attacker gaining knowledge of the plaintext passwords (e.g. using John the
Ripper).
As of py-bcrypt-0.4, this module can also be used as a Key Derivation Function
(KDF) to turn a password and salt into a cryptographic key.
tnn wrote:
: As the software seems to be ...
:
: 1) completely abandoned by upstream for several years
: 2) hasn't worked in pkgsrc for at least as long
: 3) has been removed from all linux distributions I can find
:
: ... the only reasonable choice of action is to remove it.
It operates the mozilla-rootcerts installer script in order to allow
managing the resulting output openssl certs with the package tools.
Since openssl does not support more than one directory of certificates
(sheesh) this is an abusive package - it installs directly into the
openssl certs directory even though this is a sysconfig directory that
should normally only be touched using the config files infrastructure.
And, for native openssl, it's in the root /etc outside of $PREFIX.
Nonetheless, having this package is better than not having it.
Probably at some point this and the mozilla-rootcerts package should
be folded together in some fashion; but I didn't want to do that up
front, and in particular I didn't want to muck with the installer
script in mozilla-rootcerts any more than necessary to make this
package possible. This in particular prevented e.g. installing the
certs in share/ and symlinking them into the certs directory.
As things are, if you already have the certs installed manually you
can install this package over them cleanly, and thenceforth not have
to update them by hand.
package is built independently now.
Bump PKGREVISON.
The commit message in MesaLib read:
date: 2015-01-29 23:35:43 +0100; author: nat; state: Exp;
Fix segfaults and crashing with applications that use libGLU.
* Feature #56: Treat '-' file parameter as stdin.
* Feature #57: Retain escaping of html except within code or pre tags.
* Feature #59: Write image tags with height and width attrs as raw
html to retain dimensions
- Add LICENSE as gnu-gpl-v2
(upstream)
- Update 2.3.1 to 2.3.8
---------------------
* Thu Mar 05 2009 Rahul Bhalerao <rbhalera@redhat.com> - 2.3.8
- Bug 428427 - [kn_IN][fonts-indic] - 0CB5+0CCA is wrongly rendering
- Bug 450699 - [ta_IN]Errors in "sh" and "shrI" in Lohit Tamil
font (fixed in font, needs rendering update)
- Bug 476427 - [te_IN] -
Consonant+Virama+Consonant+Virama+space renders the second
virama as a separate glyph in lohit-telugu font
- Bug 479100 - [kn_IN] Conjunct combination of U0C9D with
U0CCA/U0CCB is rendering wrongly
- Bug 483530 - [bn_IN]Lohit Bengali font cheating about character support
- Added Lohit-Assamese
- Modified README file.
--------------
CHANGES IN 1.11 2015-01-21
Changed capital "A" to be less pointy, more consistent between sizes.
Expecting hate mail.
Previously, unimplemented chars defaulted to print a blank space under X.
Now those chars are not placed in the font at all in order to allow
fontconfig to fall back to use a char from another font. (Thanks, Allen,
for pointing this out and testing the fix.)
Update DEPENDS
Upstream changes:
2.1404 2015-04-16
[BUG FIXES]
- Add Sub::Identify to prereqs. (RT #101661)
- bump List::Util prereq to avoid a memory leak (RT#101124)
[DOCUMENTATION]
- Added section to Moose::Manual::Resources to list external links related
to Moose (RT #101993, Michael LaGrasta)
dependency. Bump BUILDLINK_A{B,P}I* in buildlink3.mk due to API changes.
From NEWS:
== GNU ZRTP 4.4.0 ==
Changes the handling of HMAC and Hash contexts to avoild tool
many malloc/free calls and thus memory pointer problems.
Enhance the handling an check the nonce when using multi-stream
mode. This required a modification to the class file and some
modifications on the API. The old functions are now deprecated
but still usable. Nevertheless you should change your application
to use the new fuctions which support the new nonce handling and
checks.
Some bug fixing as well.
== GNU ZRTP 4.3.1 ==
This is a bugfix release. It fixes several compiler issues in
iOS8 Clang, Mircosoft C++ compiler (VS 2012) etc.
This release also adds a fix to address a possible problem when
using 'memset(...)' on a memory area immediately followed by a
'free(...)' call to free this memory area. Some compilers may
otpimize the code and do not call 'memset(...)'. That's bad for
software that deals with secure keys :-) . The fix removes this
possible vulnerability.
== GNU ZRTP 4.3.0 ==
This version adds some new API that provide to set retry timer
values and to get some retry counters.
Application may now set some values of the retry counters during
the discovery (Hello) and the negotiation phase. Applications may
increase the number of retries or modify the capping to support
slow or bad networks.
To get some idea about the actual number of retries during ZRTP
negotiation an application may now use the new API to get an array
of counters. The ZRTP state engine records how many retries occured
during the different protocol states.
Note: only the ZRTP initiator performs packet retries after the
discovery (Hello) phase. The responder would always return zero
alues for the other retry counters.
Because we have a new set of functions the API changed, thus it's
necessary to recompile applications that use the new library version.
== GNU ZRTP 4.2.4 ==
Only small changes to enable Android X86 (see clients/tivi/android)
as an example.
Rename functions aes_init() to aes_init_zrtp() to avoid names clashes
with other libreries that may include own AES modules.
== GNU ZRTP 4.2.3 ==
The optional SAS relay feature (refer to RFC6189, chapter 7.3) is
not longer compiled by default. If your project needs this support
then modify the CMakeLists.txt file and uncomment a 'add_definition'
statments. See comment in the CMakelists.txt file.
The reasons to disable this optional feature in the default build:
it's rarely used and some concerns about misusing this feature.
== GNU ZRTP 4.2.2 ==
A small enhancement in SRTP handling to provide a longer bit-shift
register with 128 bits. The replay now check accepts packets which
are up to 127 sequence number behing the current packet. The upper
layer (codecs) gets more packets on slower/bad networks that we may
see on mobile 3G/4G connections.
If the codecs do not remove silence then this may lead to some longer
audio replay, similar to sattelite communication.
== GNU ZRTP 4.2.1 ==
Bug fixes in the SRTP part that checks for replay and updates the ROC.
The wrong computations lead to false replay indications and to wrong
HMAC, thus they dropped to much packets, in particular under bad network
conditions.
Changed the handling the the zrtp_getSasType function the the ZrtpCWrapper.
Please check the inline documentation and the compiler warning how to
use the return value of the function.
