| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/anthy/anthy/ |
| H A D | 2ch_t.patch | 57 +�����Τ��� #CN ���μ�
112 +�������� #CN ������
115 +���� #CN �奲
231 +���ᤶ���ͤäȤġ� #CN ���ᤶ���ͤäȣ�
235 +����� #CN �����
242 +���䤷������ #CN ���䤷������
245 +���䤷������ #CN ����ɤ�����
296 +����ʤ��Ϥ�� #CN ���濺̾
415 +���� #CN ��
441 +���� #CN ��
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/arch/loongarch/ |
| H A D | irq-chip-model.rst | 140 …ngson/LoongArch-Documentation/releases/latest/download/Loongson-3A5000-usermanual-1.02-CN.pdf (中文版)
146 …ngson/LoongArch-Documentation/releases/latest/download/Loongson-7A1000-usermanual-2.00-CN.pdf (中文版)
|
| H A D | introduction.rst | 341 …hub.com/loongson/LoongArch-Documentation/releases/latest/download/LoongArch-Vol1-v1.02-CN.pdf （中文版）
347 ….com/loongson/LoongArch-Documentation/releases/latest/download/LoongArch-ELF-ABI-v2.01-CN.pdf （中文版）
|
| /openbmc/linux/certs/ |
| H A D | default_x509.genkey | 10 CN = Build time autogenerated kernel key
|
| /openbmc/u-boot/include/ |
| H A D | i8042.h | 55 #define CN 2 /* control index */ macro
|
| /openbmc/docs/security/ |
| H A D | TLS-configuration.md | 219 - `Subject` CN in `client-cert.pem`, it should match existing OpemBMC user name.
221 - `Subject` CN in `server-cert.pem`, it should match OpemBMC host name. In this
233 Issuer: C=US, ST=California, L=San Francisco, O=Intel, CN=Test CA
237 Subject: C=US, ST=California, L=San Francisco, O=Intel, CN=Test CA
268 Issuer: C=US, ST=California, L=San Francisco, O=Intel, CN=Test CA
272 Subject: C=US, ST=California, L=San Francisco, O=Intel, CN=root
303 Issuer: C=US, ST=z, L=z, O=z, OU=z, CN=bmc.example.com
307 Subject: C=US, ST=z, L=z, O=z, OU=z, CN=bmc.example.com
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | ccid.rst | 59 certutil -S -d sql:$PWD -s "CN=Fake Smart Card CA" -x -t TC,TC,TC -n fake-smartcard-ca
60 certutil -S -d sql:$PWD -t ,, -s "CN=John Doe" -n id-cert -c fake-smartcard-ca
61 …certutil -S -d sql:$PWD -t ,, -s "CN=John Doe (signing)" --nsCertType smime -n signing-cert -c fak…
62 …certutil -S -d sql:$PWD -t ,, -s "CN=John Doe (encryption)" --nsCertType sslClient -n encryption-c…
|
| /openbmc/openbmc/meta-google/recipes-extended/libconfig/ |
| H A D | libconfig-perl_0.100.bb | 5 SRC_URI = "https://cpan.metacpan.org/authors/id/C/CN/CNANGEL/Conf-Libconfig-${PV}.tar.gz"
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/freeradius/files/ |
| H A D | 0012-raddb-certs-Makefile-fix-the-existed-certificate-err.patch | 13 ERROR:There is already a certificate for /C=FR/ST=Radius/O=Example Inc./CN=user@example.org/emailAd…
19 Subject Name :/C=FR/ST=Radius/O=Example Inc./CN=user@example.org/emailAddress=user@example.org
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/ttf-fonts/source-han-sans-cn-fonts/ |
| H A D | 44-source-han-sans-cn-fonts.conf | 12 <string>Source Han Sans CN Medium</string>
|
| /openbmc/openbmc/meta-security/meta-integrity/scripts/ |
| H A D | ima-gen-local-ca.sh | 28 CN = meta-intel-iot-security example certificate signing key
|
| H A D | ima-gen-CA-signed.sh | 30 CN = meta-intel-iot-security example signing key
|
| /openbmc/u-boot/tools/ |
| H A D | k3_x509template.txt | 13 CN = TI Support
|
| /openbmc/linux/Documentation/arch/loongarch/ |
| H A D | irq-chip-model.rst | 138 …oongArch-Documentation/releases/latest/download/Loongson-3A5000-usermanual-1.02-CN.pdf (in Chinese)
144 …oongArch-Documentation/releases/latest/download/Loongson-7A1000-usermanual-2.00-CN.pdf (in Chinese)
|
| /openbmc/qemu/scripts/ |
| H A D | u2f-setup-gen.py | 106 cert.get_subject().CN = "U2F emulated"
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | usb.rst | 1029 Level 0 | CN.0 | CN.1 | [CN = connector/port #]
1036 |CN.0 |CN.1 |CN.2 |CN.3 |
1051 |_ CN.0: Dev# 2, hub, 4 ports, 12 Mbps
1052 |_ CN.0: Dev #3, mouse, 1.5 Mbps
1053 |_ CN.1:
1054 |_ CN.2: Dev #4, serial, 12 Mbps
1055 |_ CN.3:
1056 |_ CN.1:
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | openbmc_test_tools.md | 173 … <certificate filename> -out <certificate filename> -subj "/O=<Organization Name>/CN=<Common Name>"
179 …s -days 365 -keyout certificate.pem -out certificate.pem -subj "/O=XYZ Corporation /CN=www.xyz.com"
|
| /openbmc/linux/arch/arm64/boot/dts/renesas/ |
| H A D | r8a779g0-white-hawk-ard-audio-da7212.dtso | 30 * |CN34 (I2C CN) | |J1 |
|
| /openbmc/linux/drivers/phy/freescale/ |
| H A D | phy-fsl-imx8-mipi-dphy.c | 67 #define CN(x) (((x) == 1) ? 0x1f : (((CN_BUF) >> ((x) - 1)) & 0x1f)) macro
347 phy_write(phy, CN(priv->cfg.cn), DPHY_CN); in mixel_dphy_set_pll_params()
|
| /openbmc/qemu/docs/system/ |
| H A D | authz.rst | 215 CN=laptop.berrange.com,O=Berrange Home,L=London,ST=London,C=GB
253 echo "CN=laptop.qemu.org,O=QEMU Project,L=London,ST=London,C=GB" >> tls.acl
|
| H A D | tls.rst | 99 included 1 hostname in the ``CN`` field, however, usage of this field
102 multiple entries. In the future usage of the ``CN`` field may be
272 name fields and/or CN field. It also means that servers will request
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/ |
| H A D | u-boot-corstone1000.inc | 74 …openssl req -x509 -sha256 -newkey rsa:2048 -subj /CN=CRT/ -keyout ${B}/CRT.key -out ${B}/CRT.crt -…
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/freediameter/ |
| H A D | freediameter_1.5.0.bb | 111 …D_PEM} -keyout ${D}${sysconfdir}/freeDiameter/${FD_KEY} -days 3650 -subj '/CN=${FD_HOSTNAME}.${FD_…
|
| /openbmc/qemu/docs/specs/ |
| H A D | spdm.rst | 64 -subj "/CN=DMTF libspdm ECP384 responder cert"
|
| /openbmc/bmcweb/ |
| H A D | meson.options | 255 Parses the Subject CN in the format used by
265 Allows parsing the Subject CN TLS certificate in the format used by
|