mirror of
https://github.com/opnsense/src.git
synced 2026-02-14 00:04:14 -05:00
package does have BXA export approval, but the licensing strings on the dnssafe code are a bit unpleasant. The crypto is easy to restore and bind will run without it - just without full dnssec support. Obtained from: The Internet Software Consortium (www.isc.org) |
||
|---|---|---|
| .. | ||
| bsafe_link.c | ||
| cylink_link.c | ||
| dst_api.c | ||
| dst_internal.h | ||
| eay_dss_link.c | ||
| hmac_link.c | ||
| Makefile | ||
| md5.h | ||
| md5_dgst.c | ||
| md5_locl.h | ||
| prandom.c | ||
| README | ||
| rsaref_link.c | ||
| support.c | ||
This directory in BIND contains the Domain Signature Tools (dst) library. It was written by Trusted Information Systems, Inc. and integrated into BIND by John Gilmore. It is used as a generic crypto library interface by the DNS Security code in BIND. Installing Domain Signature Tools Library - dst 1. Assess available crypto libraries: if you have DNSSAFE (the default) CRYPTFLAGS must include -DDNSSAFE CRYPTINCL must include -I../dnssafe if you have RSAREF CRYPTFLAGS must include -DRSAREF CRYPTINCL must include -I<path to rsa include files> if you have BSAFE CRYPTFLAGS must include -DBSAFE CRYPTINCL must include -I<path to bsafe include files> if you want HMAC-MD5 support CRYPTFLAGs must include -DHMAC 2. Building BIND as usual will include the dst library routines into libbind.a, and link them into the BIND programs that use crypto support.