4
12
sacred_font

@infosec.pub

sacred_font 28 points 3 months ago

I left details out to be less verbose.

path: 0 24822937 24822985, hotness: undefined, score: 28, children: 0
sacred_font 26 points 3 months ago

about a month, since I ran it at about 6000 addresses / sec checking distinct addresses 4 times (round robin) or 1500 finished / sec. This was the fastest I went to avoid silent UDP drops and to hopefully not annoy my VPS hoster too much.

path: 0 24823844 24824057, hotness: undefined, score: 26, children: 3
sacred_font 24 points 3 months ago

Comparison is the thief of joy 🙃

Though if I push my scanner hard it could probably do 16k/sec on the single core and 1gig connection it is on. The problem is how reliably I could do 16k/sec over the network, since a good portion would be dropped even if the host's hardware could keep up.

I'd probably need access to enterprise-level equipment that could handle the routing load if I were to do it in 5 seconds lol, it's insane they managed to do that

path: 0 24823844 24824057 24825049 24826009, hotness: undefined, score: 24, children: 0
sacred_font 4 points 3 months ago

Unlabeled grey square at the bottom

path: 0 24826028 24834514, hotness: undefined, score: 4, children: 0
sacred_font 4 points 4 months ago

I kneel

path: 0 24145063 24148351 24148994, hotness: undefined, score: 4, children: 0
sacred_font 3 points 3 months ago

Updated

path: 0 24828207 24836398, hotness: undefined, score: 3, children: 1
sacred_font 3 points 3 months ago

commenting because it may interest you, but have you looked at the pintos project? It is an educational OS framework with the instructions on how to implement basic things like threading, user programs, file systems

https://en.wikipedia.org/wiki/Pintos

path: 0 24820964, hotness: undefined, score: 3, children: 1
sacred_font 2 points 4 months ago

I gave it some further thought and I might be completely misguided to try and max throughput. Datagrams are completely connectionless and therefore can’t know if your router’s send buffer is full or not, unless I’m missing something internal between the kernel and the router that makes sendto block (which AFAIK only happens when the socket’s send buffer is full). Therefore most “extra” datagrams I send would just be dropped anyways. I know ICMP was a dated method of congestion control but have no idea if it would still be in use for simple pings.

Edit: apparently source quench is a thing but still, no clue if the kernel intercepts this or if it is even sent in 2026 due to deprecation

path: 0 24139543 24148958 24149805 24149954, hotness: undefined, score: 2, children: 1
sacred_font 2 points 4 months ago

Is there any reason why it has to be a raw socket, rather than a dgram icmp socket? (which allows you to run as non-root) Silly me for not realizing I only needed one socket. Ofc my speed would only be at most 1-2Mbps. I currently track outgoing pings in memory so I would probably need to keep a single large circular array instead for timeout purposes -- not too different from what I'm doing currently.

path: 0 24139543 24148958, hotness: undefined, score: 2, children: 3
sacred_font 2 points 3 months ago

This was a ping scan, so it wasn't probing any TCP/UDP ports (see shodan.io). I suppose you could use ICMP control messages (Destination Unreachable) to determine if something was unused, but that assumes the other side is being friendly.

path: 0 24827972 24834484, hotness: undefined, score: 2, children: 0
sacred_font 1 point 4 months ago path: 0 24120650 24198761, hotness: undefined, score: 1, children: 0
sacred_font 1 point 4 months ago

Thank you can’t believe I forgot this

path: 0 24118604 24123455, hotness: undefined, score: 1, children: 0

thanks for using Leebra!

go to feed...