Searched full:considerations (Results 1 – 25 of 1005) sorted by relevance
12345678910>>...41
35 .Nd guide to adding security considerations sections to manual pages38 adding security considerations sections to manual pages.47 system should contain a security considerations section81 A good security considerations section114 Security considerations sections for most individual functions can follow128 This is an example security considerations section for the188 Security considerations sections for tools and commands194 This is an example security considerations section for the
9 …<title>Year 2038 considerations for uses of krb5_timestamp — MIT Kerberos Documentation</tit…42 …<a href="mailto:krb5-bugs@mit.edu?subject=Documentation__Year 2038 considerations for uses of krb5…55 <section id="year-2038-considerations-for-uses-of-krb5-timestamp">56 <h1>Year 2038 considerations for uses of krb5_timestamp<a class="headerlink" href="#year-2038-consi…59 integer in January 2038. This documentation describes considerations92 <li><a class="reference internal" href="#">Year 2038 considerations for uses of krb5_timestamp</a><…102 …l2 current"><a class="current reference internal" href="#">Year 2038 considerations for uses of kr…151 …<a href="mailto:krb5-bugs@mit.edu?subject=Documentation__Year 2038 considerations for uses of krb5…
22 … <link rel="prev" title="Year 2038 considerations for uses of krb5_timestamp" href="y2038.html" /> 34 <a href="y2038.html" title="Year 2038 considerations for uses of krb5_timestamp"122 <li class="toctree-l2"><a class="reference internal" href="y2038.html">Year 2038 considerations for…163 <a href="y2038.html" title="Year 2038 considerations for uses of krb5_timestamp"
60 <li class="toctree-l1"><a class="reference internal" href="y2038.html">Year 2038 considerations for…95 <li class="toctree-l2"><a class="reference internal" href="y2038.html">Year 2038 considerations for…
1 Year 2038 considerations for uses of krb5_timestamp6 integer in January 2038. This documentation describes considerations
279 .Sh SECURITY CONSIDERATIONS280 The same considerations as those of standard or traditional credentials-setting286 .Sy SECURITY CONSIDERATIONS
83 .Sx SECURITY CONSIDERATIONS268 .Sh SECURITY CONSIDERATIONS
39 ### TNS/E Considerations47 Linking and Loading Considerations90 Float Considerations148 follow the same considerations as for TNS/X above. SPT builds generally require182 Version Procedure (VPROC) Considerations
93 Three considerations that influenced the design of140 design considerations.172 to push device-dependent considerations
140 .Sx SECURITY CONSIDERATIONS .190 .Sh SECURITY CONSIDERATIONS
79 -C Absolute path to CA Cert (see SSL/TLS Considerations)80 -D Path to a CAdir (see SSL/TLS Considerations)128 SSL/TLS Considerations
403 -C Absolute path to CA Cert (see SSL/TLS Considerations)404 -D Path to a CAdir (see SSL/TLS Considerations)452 SSL/TLS Considerations
134 <section id="other-considerations">135 <h2>Other considerations<a class="headerlink" href="#other-considerations" title="Permalink to this…156 <li><a class="reference internal" href="#other-considerations">Other considerations</a></li>
161 4. Security Considerations203 General "stringprep" and Unicode security considerations apply. Both206 5. IANA Considerations
74 7. Name server considerations.................................... 1775 8. Root server considerations.................................... 1779 10. Security Considerations...................................... 1980 11. IANA Considerations.......................................... 20912 7. Name server considerations938 8. Root server considerations1018 10. Security Considerations1047 and [STRINGPREP], it includes the security considerations from those1098 11. IANA Considerations
182 9. Security Considerations231 10. IANA Considerations
59 .Sx SECURITY CONSIDERATIONS272 .Sh SECURITY CONSIDERATIONS
48 I/O space considerations:53 Interrupt map considerations:
20 I/O space considerations:24 Interrupt map considerations:
29 for other considerations.
35 .\" .Sh SECURITY CONSIDERATIONS
98 .Sh SECURITY CONSIDERATIONS
94 .Sh SECURITY CONSIDERATIONS
116 .Sh SECURITY CONSIDERATIONS