| /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 …]
|
| /third_party/python/Doc/library/ |
| D | security_warnings.rst | 3 .. index:: single: security considerations
5 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>`
[all …]
|
| /third_party/node/deps/cares/ |
| D | SECURITY.md | 1 c-ares security
4 This document is intended to provide guidance on how security vulnerabilities
13 Security vulnerabilities should not be entered in the project's public bug
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
[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).
13 Security vulnerabilities **should not** be entered in the project's public bug
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
[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/nghttp2/doc/sources/ |
| D | security.rst | 1 Security Process
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
35 Security advisory is disclosed on GitHub. We also post the
36 vulnerability information to `oss-security
37 <https://oss-security.openwall.org/wiki/mailing-lists/oss-security>`_
|
| /third_party/weston/man/ |
| D | weston-rdp.man | 20 On the security part, the backend supports RDP security or TLS, keys and certificates
21 must be provided to the backend depending on which kind of security is requested. The RDP
22 backend will announce security options based on which files have been given.
47 The file containing the RSA key for doing RDP security. As RDP security is known
51 The file containing the key for doing TLS security. To have TLS security you also need
55 The file containing the certificate for doing TLS security. To have TLS security you also need
62 To generate a key file to use for RDP security, you need the
67 $ winpr-makecert -rdp -silent -n rdp-security
70 This will create a rdp-security.key file.
73 You can generate a key and certificate file to use with TLS security using a typical
|
| /third_party/node/doc/guides/ |
| D | security-release-process.md | 1 # Security release process
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
5 Security Release and used to track progress on the release. It contains ***TEXT
12 `Next Security Release`, and put this checklist in the description.
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.
[all …]
|
| /third_party/node/ |
| D | SECURITY.md | 1 # Security chapter
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
24 Security bugs in third party modules should be reported to their respective
26 Security Team via [HackerOne](https://hackerone.com/nodejs-ecosystem).
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
[all …]
|
| /third_party/ntfs-3g/ntfsprogs/ |
| D | ntfssecaudit.8.in | 6 ntfssecaudit \- NTFS Security Data Auditing
14 -a full auditing of security data (Linux only)
23 -h displaying hexadecimal security descriptors saved in a file
61 Displays in an human readable form the hexadecimal security descriptors
66 Audits the volume : all the global security data on \fIvolume\fP are scanned
68 directories are also scanned and their relations to global security data
72 NTFS 3.0). Such volumes have no global security data.
78 Displays the security parameters of \fIfile\fP : its interpreted Linux mode
79 (rwx flags in octal) and Posix ACL[1], its security key if any, and its
80 security descriptor if verbose output.
[all …]
|
| /third_party/selinux/libselinux/man/man3/ |
| D | getcon.3 | 3 getcon, getprevcon, getpidcon \- get SELinux security context of a process
5 freecon, freeconary \- free memory associated with SELinux security contexts
7 getpeercon \- get security context of a peer socket
9 setcon \- set current security context of a process
60 frees the memory allocated for a security context.
76 sets the current security context of the process to a new value. Note
79 security contexts, unlike exec-based transitions performed via
107 an inconsistency among the security contexts of threads sharing
111 new security context is bounded by the old security context, where
113 policy and guarantees that the new security context has a subset of
[all …]
|
| D | selinux_restorecon.3 | 1 .TH "selinux_restorecon" "3" "20 Oct 2015" "Security Enhanced Linux" "SELinux API documentation"
4 selinux_restorecon \- restore file(s) default SELinux security contexts
17 restores file default security contexts on filesystems that support extended
34 .IR security.sehash
64 .IR security.sehash
70 .IR security.sehash
77 .IR security.sehash
206 .IR security.sehash
217 getfattr -e hex -n security.sehash /
234 .IR security.sehash
|
| /third_party/selinux/libselinux/include/selinux/ |
| D | avc.h | 34 * Return a copy of the security context corresponding to the input
45 * @ctx: input security context
48 * Look up security context @ctx in SID table, making
81 * be called to obtain a new SID for the security context.
90 * avc_get_initial_sid - get SID for an initial kernel security identifier
91 * @name: input name of initial kernel security identifier
94 * Get the context for an initial kernel security identifier specified by
147 to the given security class) into msgbuf. */
245 * callbacks will be retained, but security-event
253 * @ssid: source security identifier
[all …]
|
| /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>.
7 ## Security Incident Handling Process
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/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/include/mbedtls/ |
| D | md5.h | 7 * security risk. We recommend considering stronger message
47 * constitutes a security risk. We recommend considering
69 * constitutes a security risk. We recommend considering
81 * constitutes a security risk. We recommend considering
94 * constitutes a security risk. We recommend considering
109 * constitutes a security risk. We recommend considering
125 * constitutes a security risk. We recommend considering
142 * constitutes a security risk. We recommend considering
158 * constitutes a security risk. We recommend considering
175 * constitutes a security risk. We recommend considering
[all …]
|
| /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 …]
|
| /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/mindspore/mindspore/ccsrc/utils/ |
| D | security_py.cc | 21 // Get whether security is enable
30 // Define python wrapper to judge security enable.
31 REGISTER_PYBIND_DEFINE(security, ([](py::module *const m) { in __anone8cb6b330102()
32 auto m_sub = m->def_submodule("security", "submodule for security"); in __anone8cb6b330102()
33 (void)m_sub.def("enable_security", &EnableSecurity, "enable security"); in __anone8cb6b330102()
|
| /third_party/mindspore/ |
| D | SECURITY.md | 1 # Security for MindSpore training
3 ## Security Risk Description
7 …ference based on the data provided by users. Users need to protect data security to avoid privacy …
10 ## Security Usage Suggestions
18 # Security for MindSpore Lite
20 ## Security Risk Description
24 ## Security Usage Suggestions
|
| /third_party/ntfs-3g/src/ |
| D | ntfs-3g.c | 101 #include "security.h"
285 * Fill a security context as needed by security functions
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
[all …]
|
| /third_party/curl/ |
| D | SECURITY.md | 1 # Security Policy
3 See [docs/SECURITY-PROCESS.md](docs/SECURITY-PROCESS.md) for full details.
7 If you have found or just suspect a security problem somewhere in curl or libcurl,
10 We treat security issues with confidentiality until controlled and disclosed responsibly.
|
| /third_party/selinux/libsepol/include/sepol/policydb/ |
| D | flask_types.h | 22 * A security context is a set of security attributes
24 * by the security policy. The security context type
27 * understanding of the security policy.
42 * The set of security classes is specified in policy.
|