HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
beac0n
ruroco
Rust2024–2024
beac0n / ruroco

ruroco

Ruroco is a tool that lets you execute commands on a server by sending UDP packets. The commands are configured on the server side, so the client does not define what is going to be executed, it only picks from existing commands.

3Distinct people
4Mentions
0Explicit recommenders
556GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Ruroco is a tool that lets you execute commands on a server by sending UDP packets. The commands are configured on the server side, so the client does not define what is going to be executed, it only picks from existing commands.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval4 dated mentions

Observed mentions: 2024-08-23 10:19:07 UTC to 2024-08-28 00:46:41 UTC.

0122024-08-23 06:00:00 UTC to 2024-08-23 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 23, 06:002024-08-23 12:00:00 UTC to 2024-08-23 18:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-08-23 18:00:00 UTC to 2024-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-24 00:00:00 UTC to 2024-08-24 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-24 06:00:00 UTC to 2024-08-24 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-24 12:00:00 UTC to 2024-08-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-24 18:00:00 UTC to 2024-08-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-25 00:00:00 UTC to 2024-08-25 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-25 06:00:00 UTC to 2024-08-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-25 12:00:00 UTC to 2024-08-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 25, 12:002024-08-25 18:00:00 UTC to 2024-08-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-26 00:00:00 UTC to 2024-08-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-26 06:00:00 UTC to 2024-08-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-26 12:00:00 UTC to 2024-08-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-26 18:00:00 UTC to 2024-08-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-27 00:00:00 UTC to 2024-08-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-27 06:00:00 UTC to 2024-08-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-27 12:00:00 UTC to 2024-08-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-27 18:00:00 UTC to 2024-08-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-28 00:00:00 UTC to 2024-08-28 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 28, 00:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 23, 06:002024-08-23 06:00:00 UTC2024-08-23 12:00:00 UTC110
Aug 23, 12:002024-08-23 12:00:00 UTC2024-08-23 18:00:00 UTC202
Aug 23, 18:002024-08-23 18:00:00 UTC2024-08-24 00:00:00 UTC000
Aug 24, 00:002024-08-24 00:00:00 UTC2024-08-24 06:00:00 UTC000
Aug 24, 06:002024-08-24 06:00:00 UTC2024-08-24 12:00:00 UTC000
Aug 24, 12:002024-08-24 12:00:00 UTC2024-08-24 18:00:00 UTC000
Aug 24, 18:002024-08-24 18:00:00 UTC2024-08-25 00:00:00 UTC000
Aug 25, 00:002024-08-25 00:00:00 UTC2024-08-25 06:00:00 UTC000
Aug 25, 06:002024-08-25 06:00:00 UTC2024-08-25 12:00:00 UTC000
Aug 25, 12:002024-08-25 12:00:00 UTC2024-08-25 18:00:00 UTC000
Aug 25, 18:002024-08-25 18:00:00 UTC2024-08-26 00:00:00 UTC000
Aug 26, 00:002024-08-26 00:00:00 UTC2024-08-26 06:00:00 UTC000
Aug 26, 06:002024-08-26 06:00:00 UTC2024-08-26 12:00:00 UTC000
Aug 26, 12:002024-08-26 12:00:00 UTC2024-08-26 18:00:00 UTC000
Aug 26, 18:002024-08-26 18:00:00 UTC2024-08-27 00:00:00 UTC000
Aug 27, 00:002024-08-27 00:00:00 UTC2024-08-27 06:00:00 UTC000
Aug 27, 06:002024-08-27 06:00:00 UTC2024-08-27 12:00:00 UTC000
Aug 27, 12:002024-08-27 12:00:00 UTC2024-08-27 18:00:00 UTC000
Aug 27, 18:002024-08-27 18:00:00 UTC2024-08-28 00:00:00 UTC000
Aug 28, 00:002024-08-28 00:00:00 UTC2024-08-28 06:00:00 UTC101

What Hacker News says

4 sources
RSA allows encrypting with the private key, see https://github.com/beac0n/ruroco/blob/ce766751b51c8ff6246a2b... and decrypt with the public key, see https://github.com/beac0n/ruroco/blob/ce766751b51c8ff6246a2b... using RSA, one can easily derive the public key from its private key (see https://security.stackexchange.com/questions/172274/can-i-ge...), that's why the private key is kept safely on the client Also for SSH the public key is also stored on the server, while the private key is kept safely on the client, see https://www.ssh.com/academy/ssh/public-key-authentication#ke... SSH can also be used with RSA: https://www.ssh.com/academy/ssh/keygen#creating-an-ssh-key-p...
In Show HN: Ruroco – like port knocking, but better
mschempp·Aug 23, 2024Submission

Show HN: Ruroco – like port knocking, but better

Hey there HN! ruroco (RUn RemOte COmmand) is a tool that lets you execute commands on a server by sending UDP packets (instead of knocking on ports). the tool consist of 3 binaries: - client -> runs on your notebook/computer and sends the UDP packets - server -> receives the UDP packets and makes sure that they are valid - commander -> runs the command encoded by the data of the UDP packet if it's valid The commands are configured on the server side, so the client does not define what is going to be executed, it only picks from existing commands. I use this tool to open up the SSH port on my server via ufw, but only for the IP address from where I'm connecting, so the SSH port appears closed for everyone else, except me. This is my very first "real" rust project, so any feedback is highly appreciated :) Enjoy!
127 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.