HomeSort by: relevance | last modified time | path
    Searched refs:TLSA (Results 1 - 2 of 2) sorted by relevancy

  /src/external/ibm-public/postfix/dist/conf/
postfix-tls-script 46 # display commands to output a corresponding CSR or TLSA
84 # update the DNS with new DANE TLSA records, then wait for
98 # publishing DANE TLSA "3 1 1" or "3 1 2" records, there is
136 # .IP "\fBoutput-server-tlsa\fR [\fB-h \fIhostname\fR] [\fIkeyfile\fB...\fR]"
137 # Write to stdout a DANE TLSA RRset suitable for a port 25
148 # value is empty or equal to \fBnone\fR, then no TLSA record
584 If you publish DANE TLSA records, see:
588 https://community.letsencrypt.org/t/please-avoid-3-0-1-and-3-0-2-dane-tlsa-records-with-le-certificates/7022
629 # Otherwise, just the new keys, so that TLSA records can be updated
633 To generate TLSA records run
    [all...]
  /src/external/mpl/bind/dist/bin/tests/system/synthfromdnssec/
tests.sh 502 dig_with_opts b.wild-2-nsec-afterdata.example. @10.53.0.${ns} TLSA >dig.out.ns${ns}.test$n || ret=1
507 nextpart ns1/named.run | grep b.wild-2-nsec-afterdata.example/TLSA >/dev/null && ret=1
510 nextpart ns1/named.run | grep b.wild-2-nsec-afterdata.example/TLSA >/dev/null || ret=1
602 dig_with_opts b.wild-2-nsec-afterdata.insecure.example. @10.53.0.${ns} TLSA >dig.out.ns${ns}.test$n || ret=1

Completed in 32 milliseconds