Home
last modified time | relevance | path

Searched refs:secure (Results 1 – 90 of 90) sorted by relevance

/linux-4.1.27/arch/arm/firmware/
DKconfig12 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.1.27/Documentation/devicetree/bindings/arm/
Dsamsung-boards.txt20 - firmware node, specifying presence and type of secure firmware:
21 - compatible: only "samsung,secure-firmware" is currently supported
22 - reg: address of non-secure SYSRAM used for communication with firmware
25 compatible = "samsung,secure-firmware";
Darch_timer.txt17 - interrupts : Interrupt list for secure, non-secure, virtual and
Dtegra.txt40 Tegra supports the Trusted Foundation secure monitor. See the
Dpsci.txt9 and migration of secure software.
Dcci.txt101 secure acces to CCI registers
/linux-4.1.27/Documentation/devicetree/bindings/iommu/
Drenesas,ipmmu-vmsa.txt13 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
Darm,smmu.txt46 - calxeda,smmu-secure-config-access : Enable proper handling of buggy
47 implementations that always use secure access to
48 SMMU configuration registers. In this case non-secure
49 aliases of secure registers have to be used during
/linux-4.1.27/arch/arm/crypto/
DKconfig16 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
62 SHA-512 secure hash standard (DFIPS 180-2) implemented
102 Use a faster and more secure NEON based implementation of AES in CBC,
/linux-4.1.27/Documentation/devicetree/bindings/arm/exynos/
Dsmp-sysram.txt9 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.1.27/drivers/staging/lustre/lnet/lnet/
Dacceptor.c340 int secure = (int)((long_ptr_t)arg); in lnet_acceptor() local
392 if (secure && peer_port > LNET_ACCEPTOR_MAX_RESERVED_PORT) { in lnet_acceptor()
449 long secure; in lnet_acceptor_start() local
459 rc = accept2secure(accept_type, &secure); in lnet_acceptor_start()
467 (void *)(ulong_ptr_t)secure, in lnet_acceptor_start()
468 "acceptor_%03ld", secure)); in lnet_acceptor_start()
/linux-4.1.27/Documentation/devicetree/bindings/misc/
Dbrcm,kona-smc.txt4 used for non-secure to secure communications.
/linux-4.1.27/Documentation/devicetree/bindings/arm/omap/
Dtimer.txt32 - ti,timer-secure: Indicates the timer is reserved on a secure OMAP device
43 ti,timer-secure;
/linux-4.1.27/drivers/memory/tegra/
Dmc.c126 const char *direction, *secure; in tegra_mc_irq() local
149 secure = "secure "; in tegra_mc_irq()
151 secure = ""; in tegra_mc_irq()
199 client, secure, direction, &addr, error, in tegra_mc_irq()
/linux-4.1.27/arch/arm/mach-omap2/
DMakefile17 secure-common = omap-smc.o omap-secure.o
20 obj-$(CONFIG_ARCH_OMAP3) += $(omap-2-3-common) $(hwmod-common) $(secure-common)
21 obj-$(CONFIG_ARCH_OMAP4) += $(hwmod-common) $(secure-common)
23 obj-$(CONFIG_SOC_OMAP5) += $(hwmod-common) $(secure-common)
24 obj-$(CONFIG_SOC_AM43XX) += $(hwmod-common) $(secure-common)
25 obj-$(CONFIG_SOC_DRA7XX) += $(hwmod-common) $(secure-common)
Domap-smc.S69 mov r12, r0 @ Copy the secure service ID
Dsleep34xx.S111 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.1.27/arch/arm/mach-realview/
DKconfig85 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.1.27/Documentation/arm/
Dfirmware.txt5 Some boards are running with secure firmware running in TrustZone secure
Dtcm.txt45 be able to lock and hide one of the banks for use by the secure
/linux-4.1.27/drivers/staging/skein/
DKconfig7 Skein secure hash algorithm is one of 5 finalists from the NIST SHA3
/linux-4.1.27/Documentation/devicetree/bindings/arm/firmware/
Dtlm,trusted-foundations.txt4 Boards that use the Trusted Foundations secure monitor can signal its
/linux-4.1.27/Documentation/arm64/
Dbooting.txt11 (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
140 the virtualisation extensions) or non-secure EL1.
/linux-4.1.27/crypto/
DKconfig472 be used as a secure replacement for RIPEMD. For other use cases,
485 to be used as a secure replacement for the 128-bit hash functions
523 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
531 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
541 SHA-256 secure hash standard (DFIPS 180-2) implemented
552 SHA-512 secure hash standard (DFIPS 180-2) implemented
563 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
572 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
580 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
586 SHA-1 secure hash standard (DFIPS 180-4) implemented
[all …]
/linux-4.1.27/drivers/vfio/
DKconfig29 VFIO provides a framework for secure userspace device drivers.
/linux-4.1.27/include/uapi/linux/
Disdn.h125 int secure; /* Flag: Secure */ member
/linux-4.1.27/fs/cifs/
DKconfig32 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.1.27/arch/arm/boot/dts/
Dexynos5410-smdk5410.dts34 compatible = "samsung,secure-firmware";
Dexynos5420.dtsi399 * MDMA1 can support both secure and non-secure
401 * for boards that run in secure mode, we are getting
Dexynos5420-arndale-octa.dts30 compatible = "samsung,secure-firmware";
Dexynos5422-odroidxu3.dts33 compatible = "samsung,secure-firmware";
Dexynos4412-odroid-common.dtsi21 compatible = "samsung,secure-firmware";
Dexynos4412-origen.dts33 compatible = "samsung,secure-firmware";
Dexynos3250-monk.dts33 compatible = "samsung,secure-firmware";
Domap3.dtsi681 ti,timer-secure;
Dexynos3250-rinato.dts33 compatible = "samsung,secure-firmware";
Domap3-n900.dts16 * Default secure signed bootloader (Nokia X-Loader) does not enable L3 firewall
Domap5.dtsi77 /* PPI secure/nonsecure IRQ */
Dexynos4412-trats2.dts41 compatible = "samsung,secure-firmware";
/linux-4.1.27/Documentation/devicetree/bindings/dma/
Dqcom_bam_dma.txt15 the secure world.
Dqcom_adm.txt18 - qcom,ee: indicates the security domain identifier used in the secure world.
/linux-4.1.27/drivers/usb/wusbcore/
DKconfig23 enable the secure communication between the host and the
/linux-4.1.27/Documentation/devicetree/bindings/memory-controllers/
Drenesas-memory-controllers.txt30 - "sec" (secure interrupt)
/linux-4.1.27/Documentation/filesystems/cifs/
Dcifs.txt15 POSIX compliance, secure per-user session establishment, high
/linux-4.1.27/block/
Dioctl.c170 uint64_t len, int secure) in blk_ioctl_discard() argument
183 if (secure) in blk_ioctl_discard()
/linux-4.1.27/drivers/crypto/
DKconfig85 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.1.27/Documentation/security/
Dkeys-trusted-encrypted.txt52 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
DSmack.txt280 necessary to provide a secure domain mapping leads to the scheme being
/linux-4.1.27/arch/arm/kvm/
Dinit.S78 @ settings as the non-secure TTBCR and with T0SZ == 0.
/linux-4.1.27/Documentation/
Dvfio.txt9 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
Ddebugging-via-ohci1394.txt44 DMA by default, which is more secure but not suitable for remote debugging.
Dmodule-signing.txt240 private key must be either destroyed or moved to a secure location and not kept
DManagementStyle177 sadly that you are one too, and that while we can all bask in the secure
Ddevices.txt99 9 = /dev/urandom Faster, less secure random number gen.
/linux-4.1.27/net/ipv6/
DKconfig139 tristate "Virtual (secure) IPv6: tunneling"
147 the notion of a secure tunnel for IPSEC and then use routing protocol
/linux-4.1.27/Documentation/usb/
Dauthorization.txt66 to break it). If you need something secure, use crypto and Certificate
/linux-4.1.27/Documentation/mmc/
Dmmc-dev-attrs.txt37 to trim or secure trim operations where the minimum size is
/linux-4.1.27/arch/arm64/boot/dts/arm/
Djuno.dts96 /* last 16MB of the first memory area is reserved for secure world use by firmware */
/linux-4.1.27/drivers/block/xen-blkback/
Dblkback.c978 unsigned long secure; in dispatch_discard_io() local
995 secure = (blkif->vbd.discard_secure && in dispatch_discard_io()
1001 GFP_KERNEL, secure); in dispatch_discard_io()
/linux-4.1.27/Documentation/tpm/
Dxen-tpmfront.txt19 major component of vTPM is implemented as a separate domain, providing secure
/linux-4.1.27/drivers/of/
Dbase.c140 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.1.27/Documentation/isdn/
DREADME.HiSax540 label = linux.secure
557 /sbin/isdnctrl secure isdn0 on
599 /sbin/isdnctrl secure isdn0 on
617 /sbin/isdnctrl secure isdn0s on
DREADME314 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.1.27/
D.mailmap120 Tsuneo Yoshioka <Tsuneo.Yoshioka@f-secure.com>
/linux-4.1.27/include/net/bluetooth/
Dmgmt.h649 __u8 secure; member
Dhci_core.h1364 void mgmt_pin_code_request(struct hci_dev *hdev, bdaddr_t *bdaddr, u8 secure);
/linux-4.1.27/Documentation/networking/
Drxrpc.txt66 (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
Dip-sysctl.txt35 only intended to secure e.g. name servers in namespaces where
1661 required for secure operation of Dynamic Address Reconfiguration
Dfilter.txt1023 (In 'secure' mode verifier will reject any type of pointer arithmetic to make
/linux-4.1.27/Documentation/filesystems/
Dfuse.txt44 One of the most important features of FUSE is allowing secure,
46 filesystems. A good example is sshfs: a secure network filesystem
Dafs.txt20 This filesystem provides a fairly simple secure AFS filesystem driver. It is
Dext2.txt164 behaviour on a per-file basis. There are flags for secure deletion,
Dext4.txt610 used to store a boot loader in a secure part of
/linux-4.1.27/Documentation/scsi/
Dosd.txt109 4 in the OUT-Buffer. The ASCII illustration below depicts a secure-read with
/linux-4.1.27/drivers/net/ethernet/ti/
Dcpsw_ale.c95 DEFINE_ALE_FIELD(secure, 64, 1)
/linux-4.1.27/arch/um/
DKconfig.net193 connections passing through it (but is less secure).
/linux-4.1.27/drivers/xen/
DKconfig83 secure, but slightly less efficient.
/linux-4.1.27/net/ipv4/
DKconfig299 tristate "Virtual (secure) IP: tunneling"
307 the notion of a secure tunnel for IPSEC and then use routing protocol
/linux-4.1.27/drivers/char/
DKconfig74 to the secure memory pages however. You will need to write your
75 own secure code and reader for that.
/linux-4.1.27/net/
DKconfig117 a "proxy-based" one, is more secure but more intrusive and more
/linux-4.1.27/net/bluetooth/
Dhci_event.c3388 u8 secure; in hci_pin_code_request_evt() local
3391 secure = 1; in hci_pin_code_request_evt()
3393 secure = 0; in hci_pin_code_request_evt()
3395 mgmt_pin_code_request(hdev, &ev->bdaddr, secure); in hci_pin_code_request_evt()
Dmgmt.c7852 void mgmt_pin_code_request(struct hci_dev *hdev, bdaddr_t *bdaddr, u8 secure) in mgmt_pin_code_request() argument
7858 ev.secure = secure; in mgmt_pin_code_request()
/linux-4.1.27/arch/arm64/boot/dts/apm/
Dapm-storm.dtsi94 <1 13 0xff01>, /* Non-secure Phys IRQ */
/linux-4.1.27/arch/
DKconfig341 Enable tasks to build secure computing environments defined
/linux-4.1.27/drivers/isdn/i4l/
Disdn_net.c2796 if (cfg->secure) in isdn_net_setcfg()
2880 cfg->secure = (lp->flags & ISDN_NET_SECURE) ? 1 : 0; in isdn_net_getcfg()
/linux-4.1.27/arch/arm/
DKconfig1051 available in non-secure mode.
1065 register may not be available in non-secure mode.
1078 may not be available in non-secure mode.
/linux-4.1.27/Documentation/powerpc/
Dhvcs.txt425 using a secure method, such as SSH or sit at a hardware console.
/linux-4.1.27/init/
DKconfig1390 Note that disabling this option is more secure but might break
/linux-4.1.27/arch/x86/
DKconfig1621 secure hardware random number generator.
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt1436 which is a DOS attack. A somewhat more secure alternative would to be