Droidspaces

I know. Most users use hw-access by default, and you all want freedom. But we have to admit this: if your rooting method is compromised, if sudo, su, or the kernel is compromised, Droidspaces is compromised too. We can't prevent that. Our goal is to make devices real Linux servers that need real capabilities, not sandboxes.

Give it a try: https://t.me/DroidspacesCI/206?single

okay. we are safe now🗿

Well, you are vulnerable on Linux Desktop What happened was a Local Privilege Escalation, not a container escape. Therefore, this is a kernel issue rather than an issue with Droidspaces. However, we will work on a fix from our side if possible ❤️

It seems like Google saved all ya all asses by turning off the core Android kernel configuration necessary for this vulnerability: CONFIG_CRYPTO_USER_API_AEAD=y But that doesn’t mean we are immune to this kind of attack since non-GKI kernels exist. We still gotta block the necessary syscalls needed for this kind of attack using seccomp for the greater good.

Can anyone try the recently discovered "Copy Fail" vulnerability on Droidspaces? https://github.com/tgies/copy-fail-c/releases/tag/v0.2.0 Looks like I don't have a supported kernel. What is expected is gaining root access inside the container or total container escape.

Lemme cook 🗿

Implemented per-container resources dashboard 😋

New UI :)

New feature: Ability to backup the container as a tarball :)

thanks to gemini for this meme 🙏🏼

Droidspaces v6.0.0 has been released..! https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v6.0.0

Droidspaces is now integrable with GKI devices without breaking the Kernel ABI! 🥳 Go check out the updated guide here: https://github.com/ravindu644/Droidspaces-OSS/blob/main/Documentation/Kernel-Configuration.md#gki Thanks to @neversettle_xD and @anonymous_yolo, who made this possible and provided me with the necessary info. Droidspaces-supported kernels for OnePlus GKI devices: https://github.com/WildKernels/OnePlus_KernelSU_SUSFS #announcement

recovery-console is now open-source ! https://github.com/ravindu644/recovery-console

If you did what I did, this is the final outcome :) the Ubuntu rootfs is located inside my external SD card bought for 1$ back in 2019. That's why the booting seems slow 🗿 Anyways, to get the display output, you need my new project recovery-console.. it's still closed-source tho-

Introducing the hack behind running Droidspaces on a minimal ramdisk environment like Android recovery Low RAM usage compared to bloated TWRP/Android - a Raspberry Pi you can carry in your pocket. Read every commit from first to last to understand what I did. Touch and Wi-Fi work in stock recovery too - it's all in the commit history. Skills needed: Knowledge about Android init and partitions, SELinux patching, Linux (Kernel, Firmware, kernel modules, block devices, users/groups), etc. No step-by-step guide. If you know, you know. [ Video demonstration ] @Droidspaces

lemme cook

I'm writing an guide on our android recovery hack 🌚 I'm demonstrating how you can get a root shell inside android stock recovery, hijack the display, and boot linux.

Well, this is me running Doom at 60fps on this duct-taped Linux phone powered by Android recovery x Droidspaces 💀 @Droidspaces