| /third_party/python/Doc/library/ |
| D | security_warnings.rst | 3 .. index:: single: security considerations
8 The following modules have specific security considerations:
10 * :mod:`base64`: :ref:`base64 security considerations <base64-security>` in
12 * :mod:`cgi`: :ref:`CGI security considerations <cgi-security>`
17 basic security checks
19 <logging-eval-security>`
21 <multiprocessing-recv-pickle-security>`
23 * :mod:`random` shouldn't be used for security purposes, use :mod:`secrets`
26 dealing with untrusted sources <shelve-security>`
27 * :mod:`ssl`: :ref:`SSL/TLS security considerations <ssl-security>`
[all …]
|
| /third_party/openssl/doc/man3/ |
| D | SSL_CTX_set_security_level.pod | 5 …rity_ex_data, SSL_CTX_get0_security_ex_data, SSL_get0_security_ex_data - SSL/TLS security framework
42 the security level to B<level>. If not set the library default security level
46 retrieve the current security level.
50 the security callback associated with B<ctx> or B<s>. If not set a default
51 security callback is used. The meaning of the parameters and the behaviour
62 If an application doesn't set its own security callback the default
75 The security level corresponds to a minimum of 80 bits of security. Any
76 parameters offering below 80 bits of security are excluded. As a result RSA,
79 less than 80 bits of security. SSL version 2 is prohibited. Any cipher suite
84 Security level set to 112 bits of security. As a result RSA, DSA and DH keys
[all …]
|
| D | BN_security_bits.pod | 5 BN_security_bits - returns bits of security based on given numbers
15 BN_security_bits() returns the number of bits of security provided by a
16 specific algorithm and a particular key size. The bits of security is
20 parameters B<L> and B<N> are used to decide the bits of security, where
27 Number of security bits.
|
| /third_party/e2fsprogs/tests/d_xattr_sorting/ |
| D | expect | 4 ea_set -f /tmp/b / security.SMEG64
6 ea_set -f /tmp/b / security.imb
13 security.imb (256)
14 security.SMEG64 (256)
16 ea_get / security.imb
17 security.imb (256) = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx…
20 ea_get / security.SMEG64
21 security.SMEG64 (256) = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx…
|
| D | script | 27 echo "ea_set -f /tmp/b / security.SMEG64" >> $OUT.new
28 $DEBUGFS -w -R "ea_set -f $B / security.SMEG64" $TMPFILE >> $OUT.new 2>&1
32 echo "ea_set -f /tmp/b / security.imb" >> $OUT.new
33 $DEBUGFS -w -R "ea_set -f $B / security.imb" $TMPFILE >> $OUT.new 2>&1
50 echo "ea_get / security.imb" >> $OUT.new
51 $DEBUGFS -w -R "ea_get / security.imb" $TMPFILE >> $OUT.new 2>&1
55 echo "ea_get / security.SMEG64" >> $OUT.new
56 $DEBUGFS -w -R "ea_get / security.SMEG64" $TMPFILE >> $OUT.new 2>&1
|
| /third_party/mbedtls/ |
| D | SECURITY.md | 3 If you think you have found an Mbed TLS security vulnerability, then please
4 send an email to the security team at
5 <mbed-tls-security@lists.trustedfirmware.org>.
9 Our security process is detailled in our
10 [security
11 center](https://developer.trustedfirmware.org/w/mbed-tls/security-center/).
19 get security fixes.
|
| D | BRANCHES.md | 7 security fixes.
11 as well as all the new features and bug fixes and security fixes.
14 features added after Mbed TLS 2.26.0 and bug fixes and security fixes.
16 these only get bug fixes and security fixes.
49 crypto that was found to be weak) may need to be changed. In case security
50 comes in conflict with backwards compatibility, we will put security first,
59 before, is in case those goals would conflict with fixing a security issue, we
60 will put security first but provide a compatibility option. (So far we never
62 increase code size for a security fix.)
|
| /third_party/ntfs-3g/src/ |
| D | ntfs-3g.c | 297 scx->mapping[MAPUSERS] = ctx->security.mapping[MAPUSERS]; in ntfs_fuse_fill_security_context()
298 scx->mapping[MAPGROUPS] = ctx->security.mapping[MAPGROUPS]; in ntfs_fuse_fill_security_context()
312 return (ctx->security.mapping[MAPUSERS] != (struct MAPPING*)NULL); in ntfs_fuse_fill_security_context()
814 struct SECURITY_CONTEXT security; in ntfs_fuse_getattr() local
825 withusermapping = ntfs_fuse_fill_security_context(&security); in ntfs_fuse_getattr()
831 && !ntfs_allowed_dir_access(&security,path, in ntfs_fuse_getattr()
1034 if (ntfs_get_owner_mode(&security,ni,stbuf) < 0) in ntfs_fuse_getattr()
1379 struct SECURITY_CONTEXT security; in ntfs_fuse_opendir() local
1386 if (ntfs_fuse_fill_security_context(&security)) { in ntfs_fuse_opendir()
1399 ? !ntfs_allowed_dir_access(&security, in ntfs_fuse_opendir()
[all …]
|
| D | lowntfs-3g.c | 350 scx->mapping[MAPUSERS] = ctx->security.mapping[MAPUSERS]; in ntfs_fuse_fill_security_context()
351 scx->mapping[MAPGROUPS] = ctx->security.mapping[MAPGROUPS]; in ntfs_fuse_fill_security_context()
372 return (ctx->security.mapping[MAPUSERS] != (struct MAPPING*)NULL); in ntfs_fuse_fill_security_context()
988 struct SECURITY_CONTEXT security; in ntfs_fuse_getattr() local
994 ntfs_fuse_fill_security_context(req, &security); in ntfs_fuse_getattr()
995 res = ntfs_fuse_getstat(&security, ni, &stbuf); in ntfs_fuse_getattr()
1030 struct SECURITY_CONTEXT security; in ntfs_fuse_lookup() local
1043 if (ntfs_fuse_fill_security_context(req, &security) in ntfs_fuse_lookup()
1044 && !ntfs_allowed_access(&security,dir_ni,S_IEXEC)) { in ntfs_fuse_lookup()
1049 ntfs_fuse_fill_security_context(req, &security); in ntfs_fuse_lookup()
[all …]
|
| /third_party/nghttp2/doc/sources/ |
| D | security.rst | 12 open a new security advisory draft using `GitHub security feature
13 <https://github.com/nghttp2/nghttp2/security>`_ and discuss the
17 We write the security advisory and get CVE number from GitHub
24 security advisory (which includes all the details of the vulnerability
27 <https://oss-security.openwall.org/wiki/mailing-lists/distros>`_
30 upcoming release will have a security fix. The ``SECURITY`` label is
36 vulnerability information to `oss-security
37 <https://oss-security.openwall.org/wiki/mailing-lists/oss-security>`_
|
| /third_party/node/deps/cares/ |
| D | SECURITY.md | 1 c-ares security
4 This document is intended to provide guidance on how security vulnerabilities
15 issue to only the reporter and the project's security team.
20 The typical process for handling a new security vulnerability is as follows.
27 reference to the security nature of the commit if done prior to the public
31 privately to `c-ares-security@haxx.se`. That's an email alias that reaches a
35 security vulnerability in c-ares are ignored and no further action is
38 - A person in the security team sends an e-mail to the original reporter to
41 - The security team investigates the report and either rejects it or accepts
49 - The security team discusses the problem, works out a fix, considers the
[all …]
|
| /third_party/curl/docs/ |
| D | SECURITY-PROCESS.md | 1 curl security process
4 This document describes how security vulnerabilities should be handled in the
11 [the curl website security page](https://curl.se/docs/security.html).
19 The typical process for handling a new security vulnerability is as follows.
26 reference to the security nature of the commit if done prior to the public
34 security vulnerability in curl or libcurl are ignored and no further action
37 - A person in the security team responds to the original report to acknowledge
40 - The security team investigates the report and either rejects it or accepts
48 - The security team discusses the problem, works out a fix, considers the
57 - Write a security advisory draft about the problem that explains what the
[all …]
|
| D | BUG-BOUNTY.md | 9 Start out by posting your suspected security vulnerability directly to [curl's
12 After you have reported a security issue, it has been deemed credible, and a
26 security vulnerabilities. The amount of money that is rewarded depends on how
29 We offer reward money *up to* a certain amount per severity. The curl security
37 Everyone and anyone who reports a security problem in a released curl version
55 The curl security team is the sole arbiter if a reported flaw is subject to a
61 performed by the curl security team. The grading will be based on the CVSS
66 The curl security team first gives the vulnerability a score, as mentioned
82 curl project or its security team never actually receive any of this money,
|
| /third_party/node/doc/guides/ |
| D | security-release-process.md | 3 The security release process covers the steps required to plan/implement a
4 security release. This document is copied into the description of the Next
25 security release blog page:
49 * Subject: `Node.js security updates for all active release lines, Month Year`
53 For more information see: https://nodejs.org/en/blog/vulnerability/month-year-security-releases/
57 * [ ] CC `oss-security@lists.openwall.com` on pre-release
61 `oss-security@lists.openwall.com` as a CC.
73 * [ ] Notify [docker-node][] of upcoming security release date: ***LINK***
75 Heads up of Node.js security releases Day Month Year
77 …As per the Node.js security release process this is the FYI that there is going to be a security r…
[all …]
|
| /third_party/mindspore/mindspore/lite/java/java/fl_client/src/main/java/com/mindspore/flclient/ |
| D | SSLSocketFactoryTools.java | 23 import java.security.InvalidKeyException;
24 import java.security.KeyManagementException;
25 import java.security.NoSuchAlgorithmException;
26 import java.security.NoSuchProviderException;
27 import java.security.SignatureException;
28 import java.security.cert.Certificate;
29 import java.security.cert.CertificateException;
30 import java.security.cert.CertificateFactory;
31 import java.security.cert.X509Certificate;
205 return new java.security.cert.X509Certificate[0]; in getAcceptedIssuers()
|
| /third_party/grpc/test/cpp/qps/ |
| D | secure_sync_unary_ping_pong_test.cc | 50 SecurityParams security; in RunSynchronousUnaryPingPong() local
51 security.set_use_test_ca(true); in RunSynchronousUnaryPingPong()
52 security.set_server_host_override("foo.test.google.fr"); in RunSynchronousUnaryPingPong()
53 client_config.mutable_security_params()->CopyFrom(security); in RunSynchronousUnaryPingPong()
54 server_config.mutable_security_params()->CopyFrom(security); in RunSynchronousUnaryPingPong()
|
| /third_party/selinux/secilc/docs/ |
| D | cil_sid_statements.md | 40 (sid security)
76 This will produce an ordered list of "`kernel security unlabeled`"
80 (sid security)
82 (sidorder (kernel security))
83 (sidorder (security unlabeled))
89 Associates an SELinux security [context](#context) to a previously declared [`sid`](cil_sid_stateme…
115 <td align="left"><p>A previously declared <code>context</code> identifier or an anonymous security …
122 This shows two named security context examples plus an anonymous context:
130 (sid security)
132 (sidcontext security security_context)
|
| /third_party/iptables/extensions/ |
| D | libxt_CONNSECMARK.man | 1 This module copies security markings from packets to connections
5 .B security
12 If the packet has a security marking, copy it to the connection
16 If the packet does not have a security marking, and the connection
17 does, copy the security marking from the connection to the packet.
|
| D | libxt_SECMARK.man | 1 This is used to set the security mark value associated with the
2 packet for use by security subsystems such as SELinux. It is
4 .B security
|
| /third_party/node/ |
| D | SECURITY.md | 5 Report security bugs in Node.js via [HackerOne](https://hackerone.com/nodejs).
11 After the initial reply to your report, the security team will endeavor to keep
18 The Node.js project engages in an official bug bounty program for security
29 [Security Working Group repository](https://github.com/nodejs/security-wg/blob/HEAD/processes/third…
31 Thank you for improving the security of Node.js and its ecosystem. Your efforts
36 Here is the security disclosure policy for Node.js
38 * The security report is received and is assigned a primary handler. This
48 * On the embargo date, the Node.js security mailing list is sent a copy of the
63 ## Receiving security updates
74 [file an issue](https://github.com/nodejs/security-wg/issues/new) to discuss.
|
| /third_party/grpc/ |
| D | BUILD.gn | 550 "src/core/ext/upb-generated/udpa/annotations/security.upb.c",
551 "src/core/ext/upb-generated/udpa/annotations/security.upb.h",
710 "src/core/ext/upbdefs-generated/udpa/annotations/security.upbdefs.c",
711 "src/core/ext/upbdefs-generated/udpa/annotations/security.upbdefs.h",
988 "src/core/lib/security/authorization/authorization_engine.cc",
989 "src/core/lib/security/authorization/authorization_engine.h",
990 "src/core/lib/security/authorization/evaluate_args.cc",
991 "src/core/lib/security/authorization/evaluate_args.h",
992 "src/core/lib/security/authorization/matchers.cc",
993 "src/core/lib/security/authorization/matchers.h",
[all …]
|
| D | gRPC-C++.podspec | 133 'include/grpcpp/impl/codegen/security/auth_context.h',
164 'include/grpcpp/security/auth_context.h',
165 'include/grpcpp/security/auth_metadata_processor.h',
166 'include/grpcpp/security/credentials.h',
167 'include/grpcpp/security/credentials_impl.h',
168 'include/grpcpp/security/server_credentials.h',
169 'include/grpcpp/security/server_credentials_impl.h',
170 'include/grpcpp/security/tls_credentials_options.h',
516 'src/core/lib/security/context/security_context.h',
517 'src/core/lib/security/credentials/alts/alts_credentials.h',
[all …]
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Target/SystemZ/ |
| D | SystemZFeatures.td | 72 "message-security-assist-extension3", "MessageSecurityAssist3",
73 "Assume that the message-security-assist extension facility 3 is installed"
77 "message-security-assist-extension4", "MessageSecurityAssist4",
78 "Assume that the message-security-assist extension facility 4 is installed"
167 "message-security-assist-extension5", "MessageSecurityAssist5",
168 "Assume that the message-security-assist extension facility 5 is installed"
207 "message-security-assist-extension7", "MessageSecurityAssist7",
208 "Assume that the message-security-assist extension facility 7 is installed"
212 "message-security-assist-extension8", "MessageSecurityAssist8",
213 "Assume that the message-security-assist extension facility 8 is installed"
[all …]
|
| /third_party/mindspore/mindspore/ops/operations/ |
| D | debug_ops.py | 19 from mindspore._c_expression import security
91 if security.enable_security():
134 if security.enable_security():
190 if security.enable_security():
234 if security.enable_security():
431 if security.enable_security():
|
| /third_party/selinux/ |
| D | BUILD.gn | 127 subsystem_name = "security"
141 subsystem_name = "security"
223 subsystem_name = "security"
238 subsystem_name = "security"
252 subsystem_name = "security"
266 subsystem_name = "security"
280 subsystem_name = "security"
294 subsystem_name = "security"
308 subsystem_name = "security"
322 subsystem_name = "security"
[all …]
|