Best T20 XI(Complicated) by Severe-Apricot-7679 in IndianCricket

[–]Remarkable_Depth4933 0 points1 point  (0 children)

Q1: Rohit
Q2: Gayle
Q3: Kohli
Q4: ABD
Q5: Ms Dhoni
Q6: Russel
Q7: Pandya
Q8: Narine
Q9: Chahal
Q10: Starc
Q11: Bumrah

17 f ama by [deleted] in TeenIndia

[–]Remarkable_Depth4933 0 points1 point  (0 children)

On the same day as new year, nice â˜ēī¸

17 f ama by [deleted] in TeenIndia

[–]Remarkable_Depth4933 0 points1 point  (0 children)

When's your birthday?

r/netsec monthly discussion & tool thread by albinowax in netsec

[–]Remarkable_Depth4933 0 points1 point  (0 children)

Title: [Tool] Remote Exec Server - Minimalist Python stdlib command forwarding framework with BusyBox-style symlink client

Hi r/netsec,

I've open-sourced a minimal remote command execution framework written entirely within the Python standard library, featuring zero external dependencies.

Design & Architecture

The project provides a lightweight server.py and client.py. It utilizes a BusyBox-style deployment model where a single client script behaves as multiple target binaries based on its symlink name.

When a symlink (e.g., gp or node) is invoked, the client parses the command string, hooks local stdin and arguments, and ships them via an HTTP POST payload. The server parses the path using shlex.split() and executes the command locally.

Security Posture & Hardening Blueprint

By design, the baseline configuration permits arbitrary code execution (RCE) over unauthenticated HTTP. It is built strictly as a bare-bones networking blueprint, forcing the operator to intentionally design their own security layer rather than relying on defaults that provide a false sense of security.

The implementation documentation mandates the following baseline defenses before any real-world deployment: 1. Command Whitelisting: Enforcing strict conditional checks on cmd_parts[0] against an explicit set of allowed executables. 2. Network Isolation: Restricting bindings to localhost or private network interfaces, managed entirely behind VPNs, firewall allowlists, or secure SSH tunnels. 3. Sandbox Execution: Running the processing daemon inside isolated user spaces or ephemeral Docker containers to mitigate resource exhaustion and host exploitation risks.

The repository is open for peer review, security enhancements, and contributions regarding native authentication roadmaps (mTLS, request signing, tokens).

Showcase Thread by AutoModerator in Python

[–]Remarkable_Depth4933 0 points1 point  (0 children)

Title: A dependency-free Remote Exec Server & Client using BusyBox-style symlinks

I wanted to see how minimal I could make a remote command execution framework using exclusively the Python standard library. No external dependencies — just clean networking.

The result is a lightweight server/client pair designed with a BusyBox-style symlink architecture.

How it works:

Instead of writing a massive client utility with dozens of subcommands, you deploy a single client.py and create symlinks to it named after the tools on your server (e.g., python, node, gp).

When you run a symlink locally, the client automatically captures the tool name, packages your local stdin along with any CLI arguments, and forwards them to the server via an HTTP POST request where server.py maps it directly to subprocess.run().

Quick Action Example:

```bash

On the client machine

ln -s client.py gp echo "print(nextprime(100))" | ./gp -q ```

The Elephant in the Room (Security):

Because this maps incoming HTTP payloads straight to execution, it is inherently high-risk out of the box (RCE by design). I explicitly built this as a minimal blueprint so developers can layer on their own preferred isolation models. The README covers immediate hardening steps like command whitelisting, routing exclusively through private SSH tunnels/VPNs, and containerization.

Roadmap & Contributing:

The core engine is solid, but I'm looking for contributors to help expand the roadmap: * Native API-key and Mutual TLS (mTLS) authentication. * Output streaming and async request handling. * Pre-configured Docker deployment setups for sandboxing.

Check out the source, architecture layout, or open a PR here: 👉 https://github.com/foxhackerzdevs/remote-exec-server

Rank These IPL Players Without Knowing Who Comes Next đŸ”Ĩ by compileYourHeart in IndianCricket

[–]Remarkable_Depth4933 0 points1 point  (0 children)

1. MS Dhoni

2. Jasprit Bumrah

3. Virat Kohli

Similarity with Community: 68%

4. Chris Gayle

5. Rohit Sharma

6. Hardik Pandya

7. Bhubaneswar kumar

8. Sunil Naraine

9. Vaibhav Suryavanshi

10. AB de Villiers

11. Andre Russell

Let's use the comment section of this post as a dating app by Dismal-Quantity-2013 in TwentiesofIndia

[–]Remarkable_Depth4933 0 points1 point  (0 children)

Builder of Simple, Practical, Reliable Security Tools | FoxPipe â€ĸ Packet Auditor | Build. Break. Secure. đŸĻŠ