rya.nc
Hacker. Enby. Administrative inconvenience. Purveyor of technically sophisticated shitposts.
Suing the UK for more gender, help with my legal bills: https://enby.org.uk/
Mastodon: https://infosec.exchange/@ryanc
Non-binary trans androgynous (they/them)
3,569 posts
5,654 followers
933 following
Regular Contributor
Active Commenter
comment in response to
post
There is no way to ask me about my sex assigned at birth that will not elicit a "none of your fucking business" response.
I have no official record of it in any case.
comment in response to
post
I mean, my team would probably love it, but the lawyers I talk to might take me less seriously.
comment in response to
post
Nothing, as far as I'm concerned, but some people are boring.
comment in response to
post
From Samir Talwar:
This is the same GitHub where any commit on any fork is accessible in the original repository, right?
I wonder if you can brick someone else's repo by forking, without even opening a PR…
functional.computer
comment in response to
post
I identify as a problem, apparently GitHub's today.
comment in response to
post
They don't seem to appreciate the humor of an email address that is also a shell command injection attempt or the time zone of -2456.
comment in response to
post
I didn't say they did, I said "...I consider myself..."
comment in response to
post
As a nonbinary person I consider myself not female and not male and therefore an nth gender, for n ≥ 3, but I will use whichever facilities I feel most comfortable in.
comment in response to
post
FPU, trial division.
comment in response to
post
I resorted to binary search to calculate the cube roots.
comment in response to
post
I don't have much experience with assembly golf, so I find it hard to believe this can't be beaten.
comment in response to
post
I posted my 164 byte solution, and I spent a few hours trying to shave off another byte from there with no success.
comment in response to
post
Patching the SSH daemon to deny access based on the client id string and algorithm support seems to be sufficient to stop bots for the moment.
They're mostly just an annoyance, though. Noise in the logs.
comment in response to
post
Have to do a bunch of bookkeeping that the TCP stack would otherwise do for you?
comment in response to
post
Watching their face as the scans came in was amusing.
comment in response to
post
Also, it picks arbitrary ports for the actual transfer, and therefore requires a NAT helper.
comment in response to
post
It wasn't the best option, just the only option.
comment in response to
post
I recently learned that TFTP is just about as daft.
comment in response to
post
I gave a twentysomething software engineer a crash course on the protocol stack and socket api layers about two years ago.
Once the service was online:
"Ryan, there are so many connections that never see a request, is my code broken?"
I had them start a server with no firewall and watch tcpdump…
comment in response to
post
FTP is extremely cursed.
comment in response to
post
comment in response to
post
Anyway, I have forwarded the flight status notification.
comment in response to
post
I was thinking get a bunch of individuals organized to send complaints and make it easy for them to do so.
comment in response to
post
My plan was to mostly automate the process to send a form letter and avoid using the IPSO website entirely. Would you be interested in working with me on this? Can I have my tool submit a copy of the complaint to you as well?
comment in response to
post
Why build a conveyor built when I can build a linear magnetic accelerator?
comment in response to
post
I should have a go at wrapping their complaint form with some automation.
comment in response to
post
Even filing form letter complaints would move the needle a little.
comment in response to
post
We should get a group organized to file complaints with IPSO for every one of these articles.