ANTITREE

/dev/loop3 ro squashfs ---------------------------------------------------------~inode 0x4e21c8

uts:ns 4026532198 ----------------------------------------------------------#cap_sys_admin -eff

seccomp filt 0x1f ---------------------------------------------------------#rtt 12.4ms mtu 1500

::fe80::4a2c/64 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::[vmalloc 0xffffc90000]

antiTree

Containers, kubernetes, AI, sandboxes, security, Linux isolation

and whatever else looks interesting enough to take apart.

[SANDBOXES]
[RUNTIME]GVISORID: RTM-49GVISOR / SYSCALL 0x2A / 11:16:45
Syscalls & sandboxes
[CONTAINERS]
[CLUSTER]CONTAINERDNODE: K8S-17CGROUP V2 / CAP_SYS_ADMIN / 04:22:09
Containers
[AI AGENTS]
[INFERENCE]TOOL-CALLCTX: 128KMCP / TOKENS 4096 / 19:41:02
AI & agents

· community

BSidesROC CTF Post 3

This is a continuation of the previous posts talking about BSidesROC onion related CTF challenges.

Port of Onion (PoO)

I don’t think anyone got this one mostly because I think they were expecting that it was going to take too long.

Here’s the clue:

Sail with me on a 3 hour cruise
A storm hits us hard but we must not lose
Take any port in a storm
Just to get some place warm
There's only one there; which do you choose?


    bsidesrocxehooxr.onion

Most picked up that my terrible poem was to try and guess which port the service was running on. I thought this would be an interesting challenge to either try to adapt a port scanner to use a socks proxy or script it. I think people assumed that they’d have to scan 65535 ports but it was hosted on port 1080/TCP which is above 1024 I know but I was hoping that it would be a common port that a scanner would hit.

The ways off the top of my head you could figure this out:

Tor Ports

Answer: TOR_IS_4_LOVERS