| /freebsd/sys/contrib/device-tree/Bindings/crypto/ |
| H A D | inside-secure,safexcel-eip93.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/crypto/inside-secure,safexcel-eip93.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Inside Secure SafeXcel EIP-93 cryptographic engine
10 - Christian Marangi <ansuelsmth@gmail.com>
13 The Inside Secure SafeXcel EIP-93 is a cryptographic engine IP block
16 developed by Inside Secure and given to license to vendors.
23 EIP-93 models:
24 - EIP-93i: (basic) DES/Triple DES, AES, PRNG, IPsec ESP, SRTP, SHA1
[all …]
|
| H A D | inside-secure,safexcel.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/crypto/inside-secure,safexcel.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Inside Secure SafeXcel cryptographic engine
10 - Antoine Tenart <atenart@kernel.org>
15 - const: inside-secure,safexcel-eip197b
16 - const: inside-secure,safexcel-eip197d
17 - const: inside-secure,safexcel-eip97ies
18 - const: inside-secure,safexcel-eip197
[all …]
|
| H A D | inside-secure-safexcel.txt | 1 Inside Secure SafeXcel cryptographic engine
4 - compatible: Should be "inside-secure,safexcel-eip197b",
5 "inside-secure,safexcel-eip197d" or
6 "inside-secure,safexcel-eip97ies".
7 - reg: Base physical address of the engine and length of memory mapped region.
8 - interrupts: Interrupt numbers for the rings and engine.
9 - interrupt-names: Should be "ring0", "ring1", "ring2", "ring3", "eip", "mem".
12 - clocks: Reference to the crypto engine clocks, the second clock is
14 - clock-names: mandatory if there is a second clock, in this case the
21 - "inside-secure,safexcel-eip197" is equivalent to
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/rng/ |
| H A D | inside-secure,safexcel-eip76.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/rng/inside-secure,safexcel-eip76.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Inside-Secure HWRNG Module
10 - Jayesh Choudhary <j-choudhary@ti.com>
15 - enum:
16 - ti,omap2-rng
17 - ti,omap4-rng
18 - inside-secure,safexcel-eip76
[all …]
|
| H A D | omap_rng.txt | 1 OMAP SoC and Inside-Secure HWRNG Module
5 - compatible : Should contain entries for this and backward compatible
7 - "ti,omap2-rng" for OMAP2.
8 - "ti,omap4-rng" for OMAP4, OMAP5 and AM33XX.
9 - "inside-secure,safexcel-eip76" for SoCs with EIP76 IP block
11 - ti,hwmods: Name of the hwmod associated with the RNG module
12 - reg : Offset and length of the register set for the module
13 - interrupts : the interrupt number for the RNG module.
14 Used for "ti,omap4-rng" and "inside-secure,safexcel-eip76"
15 - clocks: the trng clock source. Only mandatory for the
[all …]
|
| H A D | omap_rng.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schema
[all...] |
| /freebsd/share/man/man4/ |
| H A D | safexcel.4 | 2 .\" SPDX-License-Identifier: BSD-2-Clause
32 .Nd Inside Secure SafeXcel-IP-97 cryptographic offload engine
37 .Bd -ragged -offset indent
46 .Bd -literal -offset indent
54 support for the cryptographic acceleration functions of the EIP-97 device
55 found on some Marvell systems-on-chip.
58 .Bl -bullet -compact
60 AES-CBC
62 AES-CTR
64 AES-XTS
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/tegra/ |
| H A D | nvidia,tegra194-cbb.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/tegra/nvidia,tegra194-cbb.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sumit Gupta <sumitg@nvidia.com>
15 multiple hierarchical sub-NOCs (Network-on-Chip) and connects various
19 by the NOCs inside the CBB. NOCs reporting errors are cluster NOCs
20 "AON-NOC, SCE-NOC, RCE-NOC, BPMP-NOC, CV-NOC" and "CBB Central NOC"
28 - For CCPLEX (CPU Complex) initiator, the driver sets ERD bit. So, the
31 - For other initiators, the ERD is disabled. So, the access issuing
[all …]
|
| /freebsd/sys/contrib/openzfs/module/lua/ |
| H A D | README.zfs | 1 # SPDX-License-Identifier: CDDL-1.0
22 ------------
30 programs, please refer to the zfs-program(1m) man page instead.
34 ------------------
38 nice-to-have, but not required for channel programs to be well-supported. As
39 such, the Lua runtime in ZFS should be updated on an as-needed basis for
44 --------------------
51 useful inside ZFS / the kernel. We have changed the runtime to use int64_t
54 neither of these make sense from inside channel programs. We have removed
57 version of Lua runs inside the kernel we must handle these failures and
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | OPENSSL_riscvcap.pod | 5 OPENSSL_riscvcap - the RISC-V processor capabilities vector
13 libcrypto supports RISC-V instruction set extensions. These
16 returned by the RISC-V Hardware Probing syscall (hwprobe) are stored
23 The environment variable is similar to the RISC-V ISA string defined in the
24 RISC-V Instruction Set Manual. It is case insensitive. Though due to the limit
25 of the environment variable parser inside libcrypto, an extension must be
47 Basic bit-manipulation
53 Carry-less multiplication
59 Single-bit instructions
65 Bit-manipulation for Cryptography
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | OPENSSL_riscvcap.3 | 1 .\" -*- mode: troff; coding: utf-8 -*-
58 .TH OPENSSL_RISCVCAP 3ossl 2025-09-30 3.5.4 OpenSSL
64 OPENSSL_riscvcap \- the RISC\-V processor capabilities vector
72 libcrypto supports RISC-V instruction set extensions. These
75 returned by the RISC-V Hardware Probing syscall (hwprobe) are stored
82 The environment variable is similar to the RISC-V ISA string defined in the
83 RISC-V Instruction Set Manual. It is case insensitive. Though due to the limit
84 of the environment variable parser inside libcrypto, an extension must be
104 Basic bit-manipulation
109 Carry-less multiplication
[all …]
|
| /freebsd/share/man/man7/ |
| H A D | sprog.7 | 31 .Nd secure programming practices
36 Writing secure applications takes a very scrutinous and pessimistic outlook.
86 Always use the proper secure idiom:
93 .Ss Set-user-ID Issues
124 A jail limits all processes inside that environment, including processes with
153 Attempting to check access with sequential non-atomic operations is a very
173 .An -nosplit
|
| /freebsd/sys/arm64/conf/ |
| H A D | std.marvell | 23 # Real-time clock support
24 device mv_rtc # Marvell Real-time Clock
27 device safexcel # Inside Secure EIP-97
37 device uart_ns8250 # ns8250-type UART driver
58 device a37x0_xtal # Marvell xtal-clock
59 device a37x0_tbg # Marvell tbg-clock
60 device a37x0_nb_periph # Marvell north-bridge peripheral clock
61 device a37x0_sb_periph # Maravell south-bridge peripheral clock
|
| /freebsd/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | nxp,bbnsm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NXP Battery-Backed Non-Secure Module
10 - Jacky Bai <ping.bai@nxp.com>
13 NXP BBNSM serves as non-volatile logic and storage for the system.
17 significant 32 bits of the real-time counter match the value in the
19 The ON/OFF logic inside the BBNSM allows for connecting directly to
26 - enum:
27 - nxp,imx93-bbnsm
[all …]
|
| /freebsd/contrib/unbound/validator/ |
| H A D | val_nsec3.h | 2 * validator/val_nsec3.h - validator NSEC3 denial of existence functions.
46 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
48 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
50 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
52 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
54 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
59 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
61 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
63 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
84 * +-+-+-+-+-+-+-+-+
[all …]
|
| /freebsd/sbin/init/ |
| H A D | init.8 | 51 and if this succeeds, begins multi-user operation.
54 commences single-user operation by giving
55 the super-user a shell on the console.
60 prevent the system from going multi-user and to instead execute
61 a single-user shell without starting the normal daemons.
63 later be made to go to multi-user by exiting the
64 single-user shell (with ^D).
80 will require that the super-user password be
81 entered before the system will start a single-user shell.
85 .Dq secure .
[all …]
|
| /freebsd/contrib/pf/authpf/ |
| H A D | authpf.8 | 4 .\" Copyright (c) 1998-2007 Bob Beck (beck@openbsd.org>. All rights reserved.
23 .Nm authpf-noip
27 .Nm authpf-noip
39 Combined with properly set up filter rules and secure switches,
52 .Nm authpf-noip
72 .Nm authpf-noip ,
76 .Pa /usr/sbin/authpf-noip .
100 process stores its rules in a separate ruleset inside a
116 .Bd -literal -offse
[all...] |
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ossl-guide-introduction.pod | 5 ossl-guide-introduction
6 - OpenSSL Guide: An introduction to OpenSSL
10 OpenSSL is a robust, commercial-grade, full-featured toolkit for general-purpose
11 cryptography and secure communication. Its features are made available via a
28 Many Operating Systems (notably Linux distributions) supply pre-built OpenSSL
29 binaries either pre-installed or available via the package management system in
40 into an appropriate directory. Inside that archive you will find a file named
46 the platform specific B<NOTES> files there is also a B<NOTES-PERL.md> file that
51 which already has a pre-built version of OpenSSL installed on it via the
55 than where the pre-built version is installed. You should B<never> replace the
[all …]
|
| /freebsd/crypto/openssh/ |
| H A D | OVERVIEW | 2 OpenSSH-1.2 and should be considered OBSOLETE. It has been left in
11 Updated 19 Oct 1999 for OpenSSH-1.2
12 Updated 20 May 2001 note obsolete for > OpenSSH-1.2
15 the auxiliary programs ssh-keygen, ssh-agent, ssh-add, and
16 make-ssh-known-hosts. The main program for each of these is in a .c
24 - These provide an arbitrary size buffer, where data can be appended.
31 - Ssh uses the GNU GZIP compression library (ZLIB).
35 - Ssh contains several encryption algorithms. These are all
42 - Uses the LibreSSL BIGNUM sublibrary.
46 - Uses arc4random() and such.
[all …]
|
| /freebsd/contrib/ntp/sntp/libevent/ |
| H A D | whatsnew-2.0.txt | 3 1. Meta-issues
16 There is now a book-in-progress that explains how to use Libevent and its
19 http://www.wangafu.net/~nickm/libevent-book/ .
37 2.1. New header layout for improved forward-compatibility
40 write good, well-supported libevent code. The new headers are divided
68 for low-level buffer manipulation are in event2/buffer.h. The
69 "bufferevent" functions for higher-level buffered IO are in
78 2.2. New thread-safe, binary-compatible, harder-to-mess-up APIs
81 non-threadsafe code, or forced code built against one version of Libevent
82 to no longer build with another. The problems with now-deprecated APIs
[all …]
|
| /freebsd/contrib/libevent/ |
| H A D | whatsnew-2.0.txt | 3 1. Meta-issues
16 There is now a book-in-progress that explains how to use Libevent and its
19 http://www.wangafu.net/~nickm/libevent-book/ .
37 2.1. New header layout for improved forward-compatibility
40 write good, well-supported libevent code. The new headers are divided
68 for low-level buffer manipulation are in event2/buffer.h. The
69 "bufferevent" functions for higher-level buffered IO are in
78 2.2. New thread-safe, binary-compatible, harder-to-mess-up APIs
81 non-threadsafe code, or forced code built against one version of Libevent
82 to no longer build with another. The problems with now-deprecated APIs
[all …]
|
| /freebsd/crypto/heimdal/doc/ |
| H A D | apps.texi | 18 loaded at run-time. Modules for some of these systems can be found in
36 siacfg -a KRB5 /usr/athena/lib/libsia_krb5.so
76 KRB5CCNAME=FILE:/tmp/krb5cc`id -u`_`ps -o ppid= -p $$`; export KRB5CCNAME
104 default entry @kbd{/usr/tcb/bin/edauth -dd default}, and add a
116 @samp{--enable-osfc2}, these programs will, however, set the login
130 you want a system that is more secure than it would otherwise be, you
131 probably got an even more secure system. Passwords will not be sent in
205 @file{ktutil -k AFSKEYFILE:KeyFile get afs@@MY.REALM}
210 kadmin> ext -k AFSKEYFILE:/usr/afs/etc/KeyFile afs@@My.CELL.NAME
213 You have to make sure you have a @code{des-cbc-md5} encryption type since that
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | ossl-guide-introduction.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OSSL-GUIDE-INTRODUCTION 7ossl"
58 .TH OSSL-GUIDE-INTRODUCTION 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-introduction
65 \&\- OpenSSL Guide: An introduction to OpenSSL
68 OpenSSL is a robust, commercial-grade, full-featured toolkit for general-purpose
69 cryptography and secure communication. Its features are made available via a
85 Many Operating Systems (notably Linux distributions) supply pre-built OpenSSL
86 binaries either pre-installed or available via the package management system in
97 into an appropriate directory. Inside that archive you will find a file named
[all …]
|
| /freebsd/sys/contrib/device-tree/src/arm64/marvell/ |
| H A D | armada-cp11x.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
8 #include <dt-bindings/interrupt-controller/mvebu-icu.h>
9 #include <dt-bindings/thermal/thermal.h>
11 #include "armada-common.dtsi"
27 thermal-zones {
28 CP11X_LABEL(thermal_ic): CP11X_NODE_NAME(ic-thermal) {
29 polling-delay-passive = <0>; /* Interrupt driven */
30 polling-delay = <0>; /* Interrupt driven */
32 thermal-sensors = <&CP11X_LABEL(thermal) 0>;
42 cooling-maps { };
[all …]
|
| /freebsd/usr.sbin/jail/ |
| H A D | jail.8 | 2 .\" SPDX-License-Identifier: BSD-2-Clause
5 .\" Copyright (c) 2008-2012 James Gritton
97 .Bl -tag -width indent
107 Exhibit a list of all configured non-wildcard jails and their parameters.
132 The jail is first removed and then re-created, as if
149 .Bl -tag -width indent
151 Clean up after an already-removed jail, running commands and operations
196 No removal-related parameters for this jail will be used \(em the jail will
201 MIB entry to the specified value inside the newly created jail.
254 If hierarchical jails exist, a partial-matching wildcard definition may
[all …]
|