how do i get this to work i tried installing it and it wouldn’t connect to my airpods? Do i need anything for xposed to make it work? @Dev-in-the-BM_2.0 @kosherboy
I never tried it. It looked cool.
Me?
Whoops, my bad it wasn’t you.
@Simple_Yid i see you had an earlier post about it what is your experience with it?
Says i need l2cap but it fails to download
Really Cool!! Interesting magisk was left last… Not sure if that’s why it’s failing but this is the log I get in check requirements
e[1mDroidspaces v5.5.0 — Checking system requirements...e[0m
e[1m[MUST HAVE]e[0m
These features are required for Droidspaces to work:
[e[1;32m✓e[0m] Root privileges
[e[1;32m✓e[0m] Linux version
[e[1;31m✗e[0m] PID namespace
e[2mProcess ID namespace isolatione[0m
[e[1;32m✓e[0m] Mount namespace
[e[1;32m✓e[0m] UTS namespace
[e[1;31m✗e[0m] IPC namespace
e[2mInter-process communication isolatione[0m
[e[1;31m✗e[0m] devtmpfs support
e[2mKernel support for devtmpfse[0m
[e[1;31m✗e[0m] cgroup devices support
e[2mControl Groups (devices controller) supporte[0m
[e[1;32m✓e[0m] pivot_root syscall
[e[1;32m✓e[0m] /proc filesystem
[e[1;32m✓e[0m] /sys filesystem
[e[1;32m✓e[0m] Seccomp support
e[1m[RECOMMENDED]e[0m
These features improve functionality but are not strictly required:
[e[1;32m✓e[0m] epoll support
[e[1;32m✓e[0m] signalfd support
[e[1;32m✓e[0m] PTY support
[e[1;32m✓e[0m] devpts support
[e[1;32m✓e[0m] Loop device
[e[1;32m✓e[0m] ext4 filesystem
[e[1;32m✓e[0m] Cgroup v2 support
[e[1;32m✓e[0m] Cgroup namespace
e[1m[OPTIONAL]e[0m
These features are optional and only used for specific functionality:
[e[1;32m✓e[0m] IPv6 support
[e[1;32m✓e[0m] FUSE support
[e[1;32m✓e[0m] TUN/TAP support
[e[1;32m✓e[0m] OverlayFS support
[e[1;32m✓e[0m] Network namespace
[e[1;32m✓e[0m] Bridge device support
[e[1;32m✓e[0m] Veth pair support
e[1mSummary:e[0m
[e[1;31m✗e[0m] 4 required feature(s) missing - Droidspaces will not work
Command executed (exit code: 0)
Requirements check completed successfully
Kernel 5.10 which is officially supported.
Lol just realized a bug. Their copy log button includes the color syntax making it confusing
Works by me, magisk, but I have a custom kernel. Lindroid working as well.
Interesting. I guess I’ll wait as they say magisk is planned and try then.
Btw it looks amazing! Is it?
I mean, it is and it isn’t. Still arm, and I like docker better then lxc but that’s just me. Fyi, you can also compile your kernel with docker support (if available…).
To me, these things are not more useful than just a nice ssh flow with shared folder I can mount on Android.
That was mostly Spanish 
Didn’t check out docker yet and wdym compile my kernel? Like run full Ubuntu?
Stuff. Too late for this 
Here’s an example that I did not read to make sure it’s current.
And here’s lindroid:
Yup it’s cus of your custom kernel.
I’m not so sure he’ll be fixing it for magisk anytime soon after seeing his response to my issue #11. Apparently magisk doesn’t allow syscalls required to create namespaces which is a fundamental part of his project. Check out the his response to my issue for more
@The-curious bro you messed up
Don’t unblur if you still wanna do the challenge
The answer is: FLAG{the_curious_never_stops_asking}
Didn’t use Kali. Not even a computer.
It’s just in plaintext in the python script. You shouldn’t be distributing the python script. It gives the answer plus you see exactly how it’s done.
Want to check now?
Didn’t look through entire script yet but still no.
- In your code you have
if not re.fullmatch(r"FLAG\{[a-z0-9_]{8,64}\}", flag):
_die("flag must match FLAG{lowercase_letters_numbers_underscores}")
if len(flag) < 10:
_die("flag is too short")
That’s an unnecessary hint that narrows down result possibilities a lot.
- It won’t work. You have the flag now in .secrets locally on your machine. It didn’t get into GitHub.
- Even if it would, it would be in plaintext in the json file
- Even if not, the user can easily inject code into the python script to see the flag in plaintext before it’s encrypted.
- Even if all were safe, it still makes it much easier to get the flag. Once you see the exact algorithm used to make the puzzle, solving it is trivial.
Conclusion: you must not upload why python script at all. You should run the script on your local machine which will create all necessary files. (The script can go back to it’s first plaintext version). Add a line into .gitignore with the name of the python file so it doesn’t get uploaded to GitHub.
Once everything is created and ready, you just run git add . … Which will upload to GitHub the ready ctf with all files and without the revealing python script.
Edit: just looked a bit further in the code and my 5th point is the strongest. While the other points are also true and not easily solvable without the solution in the conclusion, the code also reveals every piece of the puzzle. I don’t wanna post all details here cuz that would ruin the ctf but look at it
I don’t think anything that uses less than 1 GB of RAM can be compared to Electron.
Saw this some time back. It’s a scam. No?
How is it a scam?