Mark Andrews wrote:
>
> And the issue almost certainly is not providing a complete enough
> change root environment. Gost dynamically loads the crypto engine
> after named starts.
I have a lot of sympathy for anyone who encounters this problem because it
took me a long time to work out what the
And the issue almost certainly is not providing a complete enough
change root environment. Gost dynamically loads the crypto engine
after named starts.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
: Stewart, Larry C Sr CTR DISA JITC (US)
Cc: bind-users@lists.isc.org
Subject: RE: Crypto failure Issues
Stewart, Larry C Sr CTR DISA JITC (US) wrote:
> Thank you that was the trick. What impact does that have on crypto
> operations used by BIND?
GOST is the Russian equivalent of NIST
Stewart, Larry C Sr CTR DISA JITC (US) wrote:
> Thank you that was the trick. What impact does that have on crypto
> operations used by BIND?
GOST is the Russian equivalent of NIST. They publish cryptography
standards, amongst other things. There are RFCs describing how to
use GOST crypto with T
...@hermes.cam.ac.uk] On Behalf Of Tony Finch
Sent: Monday, July 27, 2015 8:27 AM
To: Stewart, Larry C Sr CTR DISA JITC (US)
Cc: bind-users@lists.isc.org
Subject: Re: Crypto failure Issues
Stewart, Larry C Sr CTR DISA JITC (US) wrote:
> I am having issues with bind failing to start due t
Stewart, Larry C Sr CTR DISA JITC (US) wrote:
> I am having issues with bind failing to start due to a crypto failure
> when I compile with the --with-openssl option when I have openssl
> version 1.0.2d or 1.0.2c
>
> Is anyone aware of any compatibility issues between bind and openssl
> version 1
...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of Ted Mittelstaedt
Sent: Friday, July 24, 2015 12:28 PM
To: bind-users@lists.isc.org
Subject: Re: Crypto failure Issues
Did you compile both openssl and bind or are you using a prebuilt binary?
There are (apparently) problems with
Did you compile both openssl and bind or are you using a prebuilt binary?
There are (apparently) problems with OpenSSL 1.0.2 on the 32 bit Solaris
10 platform. This was discussed on the openssl-users mailing list
a few months ago. The "fix" was building with an openssl 1.0.1
version on that pla
All
It occurred to me that you may need more info to assist me the logs show the
following:
Jul 23 15:55:11 nit-dns2 named[20169]: [ID 873579 daemon.notice] starting BIND
9.10.2-P2 -t /nithr -u nithr -d 2 -f
Jul 23 15:55:11 nit-dns2 named[20169]: [ID 873579 daemon.notice] built with
'--prefix=
9 matches
Mail list logo