| /linux-4.4.14/arch/arm/firmware/ |
| D | Kconfig | 12 bool "Trusted Foundations secure monitor support"
17 market) are booted with the Trusted Foundations secure monitor
18 active, requiring some core operations to be performed by the secure
21 This option allows the kernel to invoke the secure monitor whenever
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | renesas,ipmmu-vmsa.txt | 13 support secure mode two interrupts must be specified, for non-secure and
14 secure mode, in that order. For instances that don't support secure mode a
|
| D | arm,smmu.txt | 52 - calxeda,smmu-secure-config-access : Enable proper handling of buggy
53 implementations that always use secure access to
54 SMMU configuration registers. In this case non-secure
55 aliases of secure registers have to be used during
|
| D | arm,smmu-v3.txt | 18 - interrupts : Non-secure interrupt list describing the wired
|
| /linux-4.4.14/arch/arm/crypto/ |
| D | Kconfig | 16 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
26 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
36 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
45 SHA-256 secure hash standard (DFIPS 180-2) implemented
53 SHA-256 secure hash standard (DFIPS 180-2) implemented
61 SHA-512 secure hash standard (DFIPS 180-2) implemented
95 Use a faster and more secure NEON based implementation of AES in CBC,
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/exynos/ |
| D | smp-sysram.txt | 9 declaration. These nodes are of two types depending upon secure or
10 non-secure execution environment.
15 "samsung,exynos4210-sysram-ns" : for Non-secure SYSRAM
|
| /linux-4.4.14/drivers/staging/lustre/lnet/lnet/ |
| D | acceptor.c | 332 int secure = (int)((long_ptr_t)arg); in lnet_acceptor() local
384 if (secure && peer_port > LNET_ACCEPTOR_MAX_RESERVED_PORT) { in lnet_acceptor()
441 long secure; in lnet_acceptor_start() local
450 rc = accept2secure(accept_type, &secure); in lnet_acceptor_start()
458 (void *)(ulong_ptr_t)secure, in lnet_acceptor_start()
459 "acceptor_%03ld", secure)); in lnet_acceptor_start()
|
| /linux-4.4.14/Documentation/devicetree/bindings/misc/ |
| D | brcm,kona-smc.txt | 4 used for non-secure to secure communications.
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/omap/ |
| D | timer.txt | 32 - ti,timer-secure: Indicates the timer is reserved on a secure OMAP device
43 ti,timer-secure;
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/samsung/ |
| D | samsung-boards.txt | 62 - firmware node, specifying presence and type of secure firmware:
63 - compatible: only "samsung,secure-firmware" is currently supported
64 - reg: address of non-secure SYSRAM used for communication with firmware
67 compatible = "samsung,secure-firmware";
|
| /linux-4.4.14/arch/arm/mach-omap2/ |
| D | Makefile | 16 secure-common = omap-smc.o omap-secure.o
19 obj-$(CONFIG_ARCH_OMAP3) += $(omap-2-3-common) $(hwmod-common) $(secure-common)
20 obj-$(CONFIG_ARCH_OMAP4) += $(hwmod-common) $(secure-common)
22 obj-$(CONFIG_SOC_OMAP5) += $(hwmod-common) $(secure-common)
23 obj-$(CONFIG_SOC_AM43XX) += $(hwmod-common) $(secure-common)
24 obj-$(CONFIG_SOC_DRA7XX) += $(hwmod-common) $(secure-common)
|
| D | omap-smc.S | 69 mov r12, r0 @ Copy the secure service ID
|
| D | sleep34xx.S | 111 mov r12, r0 @ copy secure service ID in r12
443 mov r12, r0 @ copy secure Service ID in r12
452 mov r12, r0 @ copy secure Service ID in r12
|
| /linux-4.4.14/drivers/memory/tegra/ |
| D | mc.c | 261 const char *direction, *secure; in tegra_mc_irq() local
284 secure = "secure "; in tegra_mc_irq()
286 secure = ""; in tegra_mc_irq()
334 client, secure, direction, &addr, error, in tegra_mc_irq()
|
| /linux-4.4.14/Documentation/arm/Samsung/ |
| D | Bootloader-interface.txt | 54 3. Other (regardless of secure/non-secure mode)
|
| /linux-4.4.14/arch/arm/mach-realview/ |
| D | Kconfig | 85 bool "Allow access to the secure flash memory block"
89 Select this option if Linux will only run in secure mode on the
90 RealView PB1176 platform and access to the secure flash memory
|
| /linux-4.4.14/Documentation/arm/ |
| D | firmware.txt | 5 Some boards are running with secure firmware running in TrustZone secure
|
| D | tcm.txt | 45 be able to lock and hide one of the banks for use by the secure
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/firmware/ |
| D | tlm,trusted-foundations.txt | 4 Boards that use the Trusted Foundations secure monitor can signal its
|
| /linux-4.4.14/drivers/staging/skein/ |
| D | Kconfig | 7 Skein secure hash algorithm is one of 5 finalists from the NIST SHA3
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | arch_timer.txt | 17 - interrupts : Interrupt list for secure, non-secure, virtual and
|
| D | tegra.txt | 40 Tegra supports the Trusted Foundation secure monitor. See the
|
| D | arm,scpi.txt | 63 - compatible : should be "arm,juno-sram-ns" for Non-secure SRAM on Juno
72 - compatible : should be "arm,juno-scp-shmem" for Non-secure SRAM based
|
| D | psci.txt | 9 and migration of secure software.
|
| D | cci.txt | 102 secure acces to CCI registers
|
| /linux-4.4.14/Documentation/arm64/ |
| D | booting.txt | 11 (EL0 - EL3), with EL0 and EL1 having a secure and a non-secure
12 counterpart. EL2 is the hypervisor level and exists only in non-secure
13 mode. EL3 is the highest priority level and exists only in secure mode.
17 is passed to the Linux kernel. This may include secure monitor and
150 the virtualisation extensions) or non-secure EL1.
|
| /linux-4.4.14/drivers/vfio/ |
| D | Kconfig | 29 VFIO provides a framework for secure userspace device drivers.
|
| /linux-4.4.14/crypto/ |
| D | Kconfig | 553 be used as a secure replacement for RIPEMD. For other use cases,
566 to be used as a secure replacement for the 128-bit hash functions
604 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
612 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
623 SHA-256 secure hash standard (DFIPS 180-2) implemented
635 SHA-512 secure hash standard (DFIPS 180-2) implemented
646 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
655 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
663 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
669 SHA-1 secure hash standard (DFIPS 180-4) implemented
[all …]
|
| /linux-4.4.14/include/uapi/linux/ |
| D | isdn.h | 125 int secure; /* Flag: Secure */ member
|
| /linux-4.4.14/fs/cifs/ |
| D | Kconfig | 32 support for DFS (hierarchical name space), secure per-user
72 mounts may be less secure than mounts using NTLM or more recent
93 which are needed to mount to certain secure servers (for which more
94 secure Kerberos authentication is required). If unsure, say N.
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | qcom_bam_dma.txt | 15 the secure world.
|
| D | qcom_adm.txt | 18 - qcom,ee: indicates the security domain identifier used in the secure world.
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | exynos5410-smdk5410.dts | 34 compatible = "samsung,secure-firmware";
|
| D | exynos5420.dtsi | 388 * MDMA1 can support both secure and non-secure
390 * for boards that run in secure mode, we are getting
|
| D | exynos5420-arndale-octa.dts | 32 compatible = "samsung,secure-firmware";
|
| D | exynos5422-odroidxu3-common.dtsi | 31 compatible = "samsung,secure-firmware";
|
| D | exynos4412-odroid-common.dtsi | 22 compatible = "samsung,secure-firmware";
|
| D | exynos4412-origen.dts | 34 compatible = "samsung,secure-firmware";
|
| D | exynos3250-monk.dts | 34 compatible = "samsung,secure-firmware";
|
| D | omap3.dtsi | 682 ti,timer-secure;
|
| D | exynos3250-rinato.dts | 34 compatible = "samsung,secure-firmware";
|
| D | omap3-n900.dts | 16 * Default secure signed bootloader (Nokia X-Loader) does not enable L3 firewall
|
| D | omap5.dtsi | 77 /* PPI secure/nonsecure IRQ */
|
| D | exynos4412-trats2.dts | 42 compatible = "samsung,secure-firmware";
|
| /linux-4.4.14/drivers/usb/wusbcore/ |
| D | Kconfig | 23 enable the secure communication between the host and the
|
| /linux-4.4.14/arch/arm64/boot/dts/freescale/ |
| D | fsl-ls2080a.dtsi | 206 interrupts = <0 13 4>, /* global secure fault */
207 <0 14 4>, /* combined secure interrupt */
208 <0 15 4>, /* global non-secure fault */
209 <0 16 4>, /* combined non-secure interrupt */
|
| /linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas-memory-controllers.txt | 30 - "sec" (secure interrupt)
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | cifs.txt | 15 POSIX compliance, secure per-user session establishment, high
|
| /linux-4.4.14/Documentation/security/ |
| D | keys-trusted-encrypted.txt | 52 they are only as secure as the user key encrypting them. The master user key
53 should therefore be loaded in as secure a way as possible, preferably early in
|
| D | Smack.txt | 315 necessary to provide a secure domain mapping leads to the scheme being
|
| /linux-4.4.14/drivers/crypto/ |
| D | Kconfig | 85 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
95 SHA256 secure hash standard (DFIPS 180-2).
105 SHA512 secure hash standard.
146 and uses triple-DES to generate secure random numbers like the
|
| /linux-4.4.14/arch/arm/kvm/ |
| D | init.S | 78 @ settings as the non-secure TTBCR and with T0SZ == 0.
|
| /linux-4.4.14/Documentation/ |
| D | vfio.txt | 9 a secure, IOMMU protected environment. In other words, this allows
31 secure, more featureful userspace driver environment than UIO.
39 by far the most critical aspect for maintaining a secure environment
48 things like secure direct assignment of devices into virtual machines.
72 ensure secure user access, it's not necessarily the preferred
|
| D | debugging-via-ohci1394.txt | 44 DMA by default, which is more secure but not suitable for remote debugging.
|
| D | module-signing.txt | 272 private key must be either destroyed or moved to a secure location and not kept
|
| D | ManagementStyle | 177 sadly that you are one too, and that while we can all bask in the secure
|
| D | devices.txt | 99 9 = /dev/urandom Faster, less secure random number gen.
|
| /linux-4.4.14/net/ipv6/ |
| D | Kconfig | 157 tristate "Virtual (secure) IPv6: tunneling"
165 the notion of a secure tunnel for IPSEC and then use routing protocol
|
| /linux-4.4.14/Documentation/mmc/ |
| D | mmc-dev-attrs.txt | 37 to trim or secure trim operations where the minimum size is
|
| /linux-4.4.14/arch/arm64/boot/dts/arm/ |
| D | juno-base.dtsi | 180 /* last 16MB of the first memory area is reserved for secure world use by firmware */
|
| /linux-4.4.14/Documentation/usb/ |
| D | authorization.txt | 66 to break it). If you need something secure, use crypto and Certificate
|
| /linux-4.4.14/Documentation/tpm/ |
| D | xen-tpmfront.txt | 19 major component of vTPM is implemented as a separate domain, providing secure
|
| /linux-4.4.14/drivers/block/xen-blkback/ |
| D | blkback.c | 990 unsigned long secure; in dispatch_discard_io() local
1007 secure = (blkif->vbd.discard_secure && in dispatch_discard_io()
1013 GFP_KERNEL, secure); in dispatch_discard_io()
|
| /linux-4.4.14/drivers/of/ |
| D | base.c | 140 bool secure = strncmp(pp->name, "security-", 9) == 0; in __of_add_property_sysfs() local
150 pp->attr.attr.mode = secure ? S_IRUSR : S_IRUGO; in __of_add_property_sysfs()
151 pp->attr.size = secure ? 0 : pp->length; in __of_add_property_sysfs()
|
| /linux-4.4.14/arch/arm64/boot/dts/apm/ |
| D | apm-shadowcat.dtsi | 102 <1 13 0xff04>, /* Non-secure Phys IRQ */
|
| D | apm-storm.dtsi | 94 <1 13 0xff01>, /* Non-secure Phys IRQ */
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.HiSax | 540 label = linux.secure
557 /sbin/isdnctrl secure isdn0 on
599 /sbin/isdnctrl secure isdn0 on
617 /sbin/isdnctrl secure isdn0s on
|
| D | README | 314 for one EAZ, if the network interfaces are set to secure operation.
425 "isdnctrl secure <InterfaceName> on"
442 "isdnctrl secure <InterfaceName> off"
443 Switch off secure operation (default).
|
| /linux-4.4.14/include/net/bluetooth/ |
| D | mgmt.h | 649 __u8 secure; member
|
| D | hci_core.h | 1449 void mgmt_pin_code_request(struct hci_dev *hdev, bdaddr_t *bdaddr, u8 secure);
|
| /linux-4.4.14/ |
| D | .mailmap | 126 Tsuneo Yoshioka <Tsuneo.Yoshioka@f-secure.com>
|
| /linux-4.4.14/Documentation/networking/ |
| D | rxrpc.txt | 66 (4) A secure protocol, using the Linux kernel's key retention facility to
273 secret keys corresponding to the security types it permits. When a secure
279 (*) The name of the key a client will use to secure its communications is
475 socket then looks the server secret keys up in this keyring when secure
714 If a key is supplied then this will be used to secure the call instead of
|
| D | ip-sysctl.txt | 35 only intended to secure e.g. name servers in namespaces where
1747 required for secure operation of Dynamic Address Reconfiguration
|
| D | filter.txt | 1023 (In 'secure' mode verifier will reject any type of pointer arithmetic to make
|
| D | bonding.txt | 54 3.7 Configuring LACP for 802.3ad mode in a more secure way
1662 3.7 Configuring LACP for 802.3ad mode in a more secure way
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | fuse.txt | 44 One of the most important features of FUSE is allowing secure,
46 filesystems. A good example is sshfs: a secure network filesystem
|
| D | afs.txt | 20 This filesystem provides a fairly simple secure AFS filesystem driver. It is
|
| D | ext2.txt | 164 behaviour on a per-file basis. There are flags for secure deletion,
|
| D | ext4.txt | 610 used to store a boot loader in a secure part of
|
| /linux-4.4.14/Documentation/scsi/ |
| D | osd.txt | 109 4 in the OUT-Buffer. The ASCII illustration below depicts a secure-read with
|
| /linux-4.4.14/drivers/net/ethernet/ti/ |
| D | cpsw_ale.c | 95 DEFINE_ALE_FIELD(secure, 64, 1)
|
| /linux-4.4.14/arch/um/ |
| D | Kconfig.net | 193 connections passing through it (but is less secure).
|
| /linux-4.4.14/drivers/xen/ |
| D | Kconfig | 83 secure, but slightly less efficient.
|
| /linux-4.4.14/drivers/char/ |
| D | Kconfig | 74 to the secure memory pages however. You will need to write your
75 own secure code and reader for that.
|
| /linux-4.4.14/net/ipv4/ |
| D | Kconfig | 299 tristate "Virtual (secure) IP: tunneling"
307 the notion of a secure tunnel for IPSEC and then use routing protocol
|
| /linux-4.4.14/net/ |
| D | Kconfig | 120 a "proxy-based" one, is more secure but more intrusive and more
|
| /linux-4.4.14/net/bluetooth/ |
| D | hci_event.c | 3369 u8 secure; in hci_pin_code_request_evt() local
3372 secure = 1; in hci_pin_code_request_evt()
3374 secure = 0; in hci_pin_code_request_evt()
3376 mgmt_pin_code_request(hdev, &ev->bdaddr, secure); in hci_pin_code_request_evt()
|
| D | mgmt.c | 8081 void mgmt_pin_code_request(struct hci_dev *hdev, bdaddr_t *bdaddr, u8 secure) in mgmt_pin_code_request() argument
8087 ev.secure = secure; in mgmt_pin_code_request()
|
| /linux-4.4.14/arch/ |
| D | Kconfig | 353 Enable tasks to build secure computing environments defined
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-etm4x | 155 Description: (RW) In non-secure state, each bit controls whether instruction
|
| /linux-4.4.14/drivers/isdn/i4l/ |
| D | isdn_net.c | 2796 if (cfg->secure) in isdn_net_setcfg()
2880 cfg->secure = (lp->flags & ISDN_NET_SECURE) ? 1 : 0; in isdn_net_getcfg()
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 1064 available in non-secure mode.
1078 register may not be available in non-secure mode.
1091 may not be available in non-secure mode.
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | hvcs.txt | 425 using a secure method, such as SSH or sit at a hardware console.
|
| /linux-4.4.14/init/ |
| D | Kconfig | 1401 Note that disabling this option is more secure but might break
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig | 1645 secure hardware random number generator.
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 1436 which is a DOS attack. A somewhat more secure alternative would to be
|