-
Overview
-
redpesk OS releases
-
Security updates
- Security CVE / errata
- CVE quick look
-
Redpesk OS Tips and Tricks
-
Application Framework Manager
-
Application Framework Binder
-
APIs & Services
-
Security manager
-
OP-TEE within redpesk
-
Trusted Boot
-
Recovery features
-
redpak
-
Minimal image
- Reduce image size
- Optimizing boot time
-
Kernel fragments description
- Introduction to Linux Kernel Configuration
- 01 Disable IPC, Timers and Audit
- 02 Disable Kconfig, Scheduler and Initrd
- 03 Disable Perf, Profiling and Errata
- 04 Disable EFI, Power Management Debug and Energy Model
- 05 Disable Schedutil, CPUFreq Governors and Virtualization
- 06 Disable Kprobes and Jump Labels
- 07 Disable GCC Plugins and Function Alignment
- 08 Disable Partition Parsers
- 09 Enable Inline Spinlocks and Kernel Operations
- 10 Disable Swap, Memory Hotplug and KSM
- 11 Disable Networking IPv4, IPv6, Netfilter
- 12 Disable SCTP, VLAN, TIPC, BATMAN
- 13 Disable Wireless, Bluetooth, CAN and RFKILL
- 14 Disable PCI and Firmware
- 15 Disable GNSS and ProcEvents
- 16 Disable Block Storage NBD and AoE
- 17 Disable EEPROM and Misc Drivers
- 18 Disable Network Device Drivers
- 19 Disable PHY Drivers
- 20 Disable PPP, WLAN Coexistence, and Failover
- 21 Disable Input Devices
- 22 Disable Serial, TTY and TPM
- 23 Disable I2C, Power and Sensor Drivers
- 24 Disable MFD, Display and Media Drivers
- 25 Disable USB, Sound, RTC and VirtIO
- 26 Disable Filesystem Encodings and Compatibility
- 27 Enable Minimal Cryptographic Core with SHA3 and XTS
- 28 Disable Hardware Cryptography, Keep DRBG and Jitter Entropy
- 29 Disable Kernel Debugging Features
- 30 Disable Filesystem Verity and SecurityFS
-
Zephyr in Redpesk
-
PERM-CHECK extension
-
Mender redpesk (OTA)
-
Hardware support
- Download images
- Image metrics
- Trusted Boot
- Graphical support
- Boards - ARM64
- Boards - x86_64
- Boards - Virtual
- Boards - Archived (legacy)
- Miscs
-
Building microservices natively within SDK container
-
Building microservices and framework from sources
Permissions
In the sec-lsm-manager, the following system permissions are used : redpesk-permissions
Cynagora
Permissions are sent and stored in cynagora.
For example, if we add the permission urn:redpesk:permission::partner:scope-platform
to a demo-app we will have :
CLIENT SESSION USER PERMISSION RESULT EXPIRE
demo-app * * urn:redpesk:permission::partner:scope-platform yes forever
For more details on cynagora: sec-cynagora
Mandatory Access Control
At the moment permissions only have an impact on SELinux.
They allow adding authorizations to an application.
For example the urn:redpesk:permission::partner:scope-platform permission will allow access to the /var/scope-platform folder.
Here is a list of currently supported permissions and their effect :
- urn:redpesk:permission::partner:scope-platform
Allows access to the
/var/scope-platformfolder - urn:redpesk:permission::partner:create-can-socket
Allows creation of a can socket and writing to it
- urn:redpesk:permission::partner:execute-shell
Allows execution of shell and programs in bin directories
- urn:redpesk:permission::partner:manage-tmp
Allows managing all files types in
/tmp - urn:redpesk:permission::partner:manage-user-shared
Allows managing all files types in
/run/user/[id]/usrshr/