| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/ |
| H A D | MultiFactorAuthConfiguration.interface.yaml | 2 This interface defines multi-factor authentication configuration. This
7 - name: Enabled
11 Multi-factor authentication configuration. This interface will be
12 implemented by user manager D-bus object to support user's MFA
15 - name: Supported
18 - readonly
20 This property is read only for populating allowed multi-factor
21 authentication types. When there are no multi-factor authentication
26 - name: Type
28 Multi-factor authentication type enumeration, Types of multi-factor
[all …]
|
| H A D | TOTPAuthenticator.interface.yaml | 2 This interface defines methods and properties required for Time-based
3 One-time Password (TOTP) multi-factor authentication at user level to
4 support multi-factor authentication secret key setup for each user. This
9 - name: CreateSecretKey
11 This method setup Time-based One-time Password (TOTP) authenticator
15 - name: SecretKey
21 - xyz.openbmc_project.Common.Error.UnsupportedRequest
22 - xyz.openbmc_project.Common.Error.NotAllowed
24 - name: VerifyOTP
26 This method verifies OTP with Time-based One-time Password
[all …]
|
| /openbmc/qemu/crypto/ |
| H A D | rsakey.h | 25 #include "qemu/host-utils.h"
32 * Multiple precious integer, encoded as two' complement,
48 /* The first factor */
50 /* The second factor */
52 /* The first factor's exponent */
54 /* The second factor's exponent */
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | dra7xx-clocks.dtsi | 12 #clock-cells = <0>;
13 compatible = "ti,dra7-atl-clock";
18 #clock-cells = <0>;
19 compatible = "ti,dra7-atl-clock";
24 #clock-cells = <0>;
25 compatible = "ti,dra7-atl-clock";
30 #clock-cells = <0>;
31 compatible = "ti,dra7-atl-clock";
36 #clock-cells = <0>;
37 compatible = "fixed-clock";
[all …]
|
| H A D | omap3xxx-clocks.dtsi | 12 #clock-cells = <0>;
13 compatible = "fixed-clock";
14 clock-frequency = <16800000>;
18 #clock-cells = <0>;
19 compatible = "ti,mux-clock";
25 #clock-cells = <0>;
26 compatible = "ti,divider-clock";
28 ti,bit-shift = <6>;
29 ti,max-div = <3>;
31 ti,index-starts-at-one;
[all …]
|
| /openbmc/phosphor-user-manager/ |
| H A D | mfa_pam | 3 # Google Authenticator for two-factor authentication.
4 auth required pam_google_authenticator.so secret=/home/${USER}/.config/phosphor-user-mana…
|
| /openbmc/openbmc/meta-security/dynamic-layers/meta-python/recipes-security/mfa/ |
| H A D | python3-privacyidea_3.9.1.bb | 2 …two-factor authentication like OTP tokens, SMS, smartphones or SSH keys. Using privacyIDEA you can…
5 LICENSE = "AGPL-3.0-only"
14 python3-setuptools-scm-native \
18 rm -fr ${D}${libdir}/${PYTHON_DIR}/site-packages/tests
22 GROUPADD_PARAM:${PN} = "--system privacyidea"
23 USERADD_PARAM:${PN} = "--system -g privacyidea -o -r -d /opt/${BPN} \
24 --shell /bin/false privacyidea"
28 RDEPENDS:${PN} = " bash perl freeradius-mysql freeradius-utils"
29 RDEPENDS:${PN} += "python3 python3-alembic python3-babel python3-bcrypt"
30 RDEPENDS:${PN} += "python3-beautifulsoup4 python3-cbor2 python3-certifi python3-cffi python3-charde…
[all …]
|
| /openbmc/u-boot/board/intel/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0+
15 Intel quad-core Atom Processor E3800 with dual-channel DDR3L SODIMM
23 mini-ITX form factor containing the Intel Braswell SoC, which has
24 a 64-bit quad-core, single-thread, Intel Atom processor, along with
25 serial console, 10/100/1000 Ethernet, SD-Card, USB 2/3, SATA, PCIe,
26 some GPIOs, one HDMI and two DP video out.
50 eMMC flash on board, Wi-Fi, Bluetooth 4 and USB controllers.
56 Arduino-certified development and prototyping boards based on Intel
57 architecture. It includes an Intel Quark SoC X1000 processor, a 32-bit
58 single-core, single-thread, Intel Pentium processor instrunction set
[all …]
|
| /openbmc/phosphor-fan-presence/monitor/example/ |
| H A D | config.json | 6 "The first fan in the system that has two sensor(dual rotor) feedbacks",
7 "that are allowed to deviate from any given target by 15% for up-to 30",
10 "object's feedback speed is adjusted by a factor of 1.45 and offset",
11 "by -909 to accomodate how its hardware reacts to any given target. It",
19 "a poweron to allow the fan to spin-up."
37 "factor": 1.45, number
38 "offset": -909
59 "a poweron to allow the fan to spin-up."
94 "deviate from any given target by 15% for up-to 30 seconds before",
98 "applies a factor of 21 and offset of 1600 to accomodate the",
[all …]
|
| /openbmc/u-boot/drivers/ddr/marvell/a38x/ |
| H A D | mv_ddr_common.c | 1 // SPDX-License-Identifier: GPL-2.0
22 * using 97.4% inverse factor per JEDEC Standard No. 21-C, 4.1.2.L-4:
31 /* round division of two positive integers to the nearest whole number */
|
| /openbmc/u-boot/arch/arm/mach-aspeed/ast2600/ |
| H A D | Kconfig | 12 bool "EVB-AST2600"
15 EVB-AST2600 is Aspeed evaluation board for AST2600A0 chip.
16 It has 512M of RAM, 32M of SPI flash, two Ethernet ports,
21 bool "FPGA-AST2600"
24 FPGA-AST2600 is Aspeed FPGA board for AST2600 chip.
26 most implementation is co-code with EVB-AST2600.
29 bool "SLT-AST2600"
32 SLT-AST2600 is Aspeed SLT board for AST2600 chip.
35 bool "AST2600-IBM"
38 AST2600-IBM is IBM boards for AST2600 BMC based P0WER10+ servers
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | pmbus_utils.hpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
48 * as output current, input voltage, and temperature. Two byte value with
49 * an 11-bit, two's complement mantissa and a 5-bit, two's complement
55 * Linear data format used for values related to voltage output. Two
56 * byte (16-bit), unsigned integer that is raised to the power of an
57 * exponent. The exponent is not stored within the two bytes.
71 * Linear scale that uses a two byte unsigned binary integer with a scaling
72 * factor.
87 * Half-precision floating point format that follows the IEEE-754 standard
101 * - Linear format: value is an exponent
[all …]
|
| /openbmc/u-boot/board/freescale/ls1021aqds/ |
| H A D | README | 2 --------
6 ------------------
8 is built on Layerscape architecture, the industry's first software-aware,
9 core-agnostic networking architecture to offer unprecedented efficiency
12 A member of the value-performance tier, the QorIQ LS1021A processor provides
13 extensive integration and power efficiency for fanless, small form factor
14 enterprise networking applications. Incorporating dual ARM Cortex-A7 cores
15 running up to 1.0 GHz, the LS1021A processor delivers pre-silicon CoreMark
17 security features and the broadest array of high-speed interconnects and
18 optimized peripheral features ever offered in a sub-3 W processor.
[all …]
|
| /openbmc/u-boot/board/freescale/ls1021atwr/ |
| H A D | README | 2 --------
6 ------------------
8 is built on Layerscape architecture, the industry's first software-aware,
9 core-agnostic networking architecture to offer unprecedented efficiency
12 A member of the value-performance tier, the QorIQ LS1021A processor provides
13 extensive integration and power efficiency for fanless, small form factor
14 enterprise networking applications. Incorporating dual ARM Cortex-A7 cores
15 running up to 1.0 GHz, the LS1021A processor delivers pre-silicon CoreMark
17 security features and the broadest array of high-speed interconnects and
18 optimized peripheral features ever offered in a sub-3 W processor.
[all …]
|
| /openbmc/u-boot/arch/arm/mach-rockchip/rk3399/ |
| H A D | Kconfig | 10 with full function and phisical connectors support like type-C ports,
11 usb2.0 host ports, LVDS, JTAG, MAC, SDcard, HDMI, USB-2-serial...
14 bool "Theobroma Systems RK3399-Q7 (Puma)"
16 The RK3399-Q7 (Puma) is a system-on-module (designed and
18 in a Qseven-compatible form-factor (running of a single 5V
19 supply and exposing its external interfaces on a MXM-230
22 Key features of the RK3399-Q7 include:
23 * on-module USB 3.0 hub (2x USB 3.0 host + 1x USB 2.0 host)
24 * USB 3.0 dual-role
25 * on-module Micrel KSZ9031 GbE PHY
[all …]
|
| /openbmc/u-boot/board/freescale/mpc8349itx/ |
| H A D | README | 1 Freescale MPC8349E-mITX and MPC8349E-mITX-GP Boards
2 ---------------------------------------------------
6 The MPC8349E-mITX and MPC8349E-mITX-GP are reference boards featuring
7 the Freescale MPC8349E processor in a Mini-ITX form factor.
9 The MPC8349E-mITX-GP is an MPC8349E-mITX with the following differences:
11 A) One 8MB on-board flash EEPROM chip, instead of two.
14 D) No Mini-PCI slot
15 E) No Vitesse 7385 5-port Ethernet switch
16 F) No 4-port USB Type-A interface
21 Guide. Of particular interest to U-Boot developers is jumper J22:
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 253 | 4 # Test qemu-img vs. unaligned images; O_DIRECT version
51 # going to be a factor of 1 MB
52 size=$((1 * 1024 * 1024 - 1))
54 # qemu-img create rounds size up to BDRV_SECTOR_SIZE
56 $QEMU_IMG map --output=json --image-opts \
61 truncate --size=$size "$TEST_IMG"
62 $QEMU_IMG map --output=json --image-opts \
66 # qemu-io with O_DIRECT always writes whole physical sectors. Again,
69 offset=$((1 * 1024 * 1024 - 64 * 1024))
70 $QEMU_IO -c "w $offset $((size - offset))" "$TEST_IMG" | _filter_qemu_io
[all …]
|
| /openbmc/u-boot/board/sbc8349/ |
| H A D | README | 3 U-Boot for Wind River SBC834x Boards
7 The Wind River SBC834x board is a 6U form factor (not CPCI) reference
8 design that uses the MPC8347E or MPC8349E processor. U-Boot support
9 for this board is heavily based on the existing U-Boot support for
14 difference in the two is the level of PCI functionality.
33 Note that U-Boot versions up to and including 2009.06 had essentially
34 two copies of U-Boot in flash; one at the very beginning, which set
36 As of this point in time, the two have been combined into just one
39 Use of the U-Boot command "fli" will indicate what parts are in use.
40 Details for storing U-Boot to flash using a Wind River ICE can be found
[all …]
|
| /openbmc/docs/designs/ |
| H A D | virtual-sensors.md | 5 Created: 2020-05-13
10 data and some other factor like fan speed for temperature sensors, some complex
14 1. Airflow: Function of Fan RPM reported in units of cubic-feet per second.
15 2. Voltage delta between two ADC inputs. When the actual diff is what which
31 - a daemon to create and monitor each sensor defined in config file and update
33 - Every virtual sensor will be waiting for event for change in dbus value of
35 - Sensor parameter can be any sensor dbus path and it also supports chaining of
37 - a dbus interface like other sensors to allow other services to access its data
38 - capability to read parameter details from config file
39 - capability to read a algorithm string from config file and use the same
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | AccountService.v1_18_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
20 "OEM": "An OEM-specific external authentication or directory service.",
25 …count provider shall be a Microsoft Active Directory Technical Specification-conformant service. …
26 …l account provider shall be an RFC4511-conformant service. The `ServiceAddresses` property shall …
27 …-conformant service. The `ServiceAddresses` property shall contain RFC3986-defined URIs that corr…
28 …rvice": "The external account provider shall be a DMTF Redfish Specification-conformant service. …
29 …l account provider shall be an RFC8907-conformant service. The `ServiceAddresses` property shall …
42 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
57 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | AccountService.v1_18_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
20 "OEM": "An OEM-specific external authentication or directory service.",
25 …count provider shall be a Microsoft Active Directory Technical Specification-conformant service. …
26 …l account provider shall be an RFC4511-conformant service. The `ServiceAddresses` property shall …
27 …-conformant service. The `ServiceAddresses` property shall contain RFC3986-defined URIs that corr…
28 …rvice": "The external account provider shall be a DMTF Redfish Specification-conformant service. …
29 …l account provider shall be an RFC8907-conformant service. The `ServiceAddresses` property shall …
42 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
57 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
[all …]
|
| /openbmc/u-boot/board/freescale/ls2080aqds/ |
| H A D | README | 2 --------
3 The LS2080A Development System (QDS) is a high-performance computing,
10 --------------------
11 Please refer arch/arm/cpu/armv8/fsl-layerscape/doc/README.soc for LS2080A,
15 -----------------------
16 - SERDES Connections, 16 lanes supporting:
17 - PCI Express - 3.0
18 - SGMII, SGMII 2.5
19 - QSGMII
20 - SATA 3.0
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/valkey/valkey/ |
| H A D | valkey.conf | 6 # ./valkey-server /path/to/valkey.conf
24 # to customize a few per-server settings. Include files can include
88 protected-mode yes
96 # In high requests-per-second environments you need an high backlog in order
101 tcp-backlog 511
117 # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
118 # of communication. This is useful for two reasons:
130 tcp-keepalive 300
139 # supervised no - no supervision interaction
140 # supervised upstart - signal upstart by putting Redis into SIGSTOP mode
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/redis/redis/ |
| H A D | redis.conf | 6 # ./redis-server /path/to/redis.conf
24 # to customize a few per-server settings. Include files can include
88 protected-mode yes
96 # In high requests-per-second environments you need an high backlog in order
101 tcp-backlog 511
117 # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
118 # of communication. This is useful for two reasons:
130 tcp-keepalive 300
139 # supervised no - no supervision interaction
140 # supervised upstart - signal upstart by putting Redis into SIGSTOP mode
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/redis/redis-7.2.8/ |
| H A D | redis.conf | 6 # ./redis-server /path/to/redis.conf
24 # to customize a few per-server settings. Include files can include
88 protected-mode yes
96 # In high requests-per-second environments you need an high backlog in order
101 tcp-backlog 511
117 # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
118 # of communication. This is useful for two reasons:
130 tcp-keepalive 300
139 # supervised no - no supervision interaction
140 # supervised upstart - signal upstart by putting Redis into SIGSTOP mode
[all …]
|