prologic
@twtxt.net
Follow
"Problems are Solved by Method" 🇦🇺👨💻👨🦯🏹♔ 🏓⚯ 👨👩👧👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)
Block / Report User
If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!
You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.
@prologic does not follow you (they may not see your replies!)
Recent Twts
Recent twts from prologic
#sy2nsaq
(#bbnfuvq) @lyse@lyse.isobeef.org I’ll fix it tonight Sadly I have to rebuild the index 🤦♂️
#f5z4u5a
(#bgoecxa) @lyse@lyse.isobeef.org This ☝️
#joyhtaa
Oh I forgot again 🤦♂️ Last Saturday of the month, so if anyone’s up for a friendly catch up over video tomorrow? Same time, same place 👌
#vyd7h3a
(#kwepmhq) @bender@twtxt.net Weird dunno what to say🤣
#z6h6lea
(#kwepmhq) @bender@twtxt.net Huh? 🤔
#lr6jm3a
(#2rxkcca) Also FWIW this is all my fault for writing shitty vulnerable code 🤣 So blame me! I’m sorry 🙏
#qbhy3aa
(#2rxkcca) FWIW I’m still trying to find the the cause of the mult-GB avatars that both @stigatle@yarn.stigatle.no and @abucci@anthony.buc.ci ’s pods were both teying yo download. The flaw has since been fixed in the code but I’m still trying to investigate the source 🤞
#67izzzq
(#2qczosq) @bender@twtxt.net Hehe 🤣
#kdylkbq
Hmmm something happened last night at ~3am (AEST) that decrased traffic to my pod quite considerably… Hmmm? Anyone have any ideas? 💡
#juhuf5a
(#rdeh4dq) @abucci@anthony.buc.ci No worries! All in the name of better reliability and security 😅
#antz3fq
(#4ljpfuq) @stigatle@yarn.stigatle.no Thanks! Sooo cold 🥶
#az3enqa
(#2rxkcca) @stigatle@yarn.stigatle.no no problems 👌 one problem solved at least 🤣
#mif74ta
Anyway, I’m gonna have to go to bed… We’ll continue this on the weekend. Still trying to hunt down some kind of suspected mult-GB avatar using @stigatle@yarn.stigatle.no ’s pod’s cache:
$ (echo "URL Bytes"; sort -n -k 2 -r < avatars.txt | head) | column -t
URL Bytes
https://birkbak.neocities.org/avatar.jpg 667640
https://darch.neocities.org/avatar.png 652960
http://darch.dk/avatar.png 603210
https://social.naln1.ca/media/0c4f65a4be32ff3caf54efb60166a8c965cc6ac7c30a0efd1e51c307b087f47b.png 327947
...
But so far nothing much… Still running the search…
#4ljpfuq
(#2rxkcca) Out of interest, are you able to block whole ASN(s)? I blocked the entirely of teh AWS and Facebook ASN(s) recently.
#jdbq3la
(#2rxkcca) @abucci@anthony.buc.ci Oh 🤣 Well my IP is a known subnet and static, so if you need to know what it is, Email me 😅
#at366ma
(#2rxkcca) @abucci@anthony.buc.ci Seems to be okay now hmmm
#6if5wwq
(#qv5sgja) @abucci@anthony.buc.ci Hmm I can see your twts on my pod now 🤔
#jefrymq
@abucci@anthony.buc.ci / @abucci@anthony.buc.ci Any interesting errors pop up in the server logs since the the flaw got fixed (unbounded receieveFile()
)? 🤔
#2rxkcca
Hmmm 🧐
for url in $(jq -r '.Twters[].avatar' cache.json | sed '/^$/d' | grep -v -E '(twtxt.net|anthony.buc.ci|yarn.stigatle.no|yarn.mills.io)' | sort -u); do echo "$url $(curl -I -s -o /dev/null -w '%header{content-length}' "$url")"; done
...
😅 Let’s see… 🤔
#axhnc6a
(#ve43paq) @stigatle@yarn.stigatle.no The one you sent is fine. I’m inspecting it now. I’m just saying, do yourself a favor and nuke your pod’s garbage cache 🤣 It’ll rebuild automatically in a much more prestine state.
#fx2mzfq
(#ve43paq) That was also a source of abuse that also got plugged (being able to fill up the cache with garbage data)
#pa54ixq
(#ve43paq) Ooof
$ jq '.Feeds | keys[]' cache.json | wc -l
4402
If you both don’t mind dropping your caches. I would recommend it. Settings -> Poderator Settings -> Refresh cache.
#mwe4fhq
(#ve43paq) @stigatle@yarn.stigatle.no Thank you! 🙏
#dpclfsa
(#ve43paq) @stigatle@yarn.stigatle.no Ta. I hope my theory is right 😅
#jjpj3ra
(#ve43paq) But just have a look at the yarnd
server logs too. Any new interesting errors? 🤔 No more multi-GB tmp files? 🤔
#bg6ssma
(#ve43paq) @stigatle@yarn.stigatle.no You want to run backup_db.sh
and dump_cache.sh
They pipe JSON to stdout and prompt for your admin password. Example:
URL=<your_pod_url> ADMIN=<your_admin_user> ./tools/dump_cache.sh > cache.json
#d2lvjma
(#ve43paq) Just thinking out loud here… With that PR merged (or if you built off that branch), you might hopefully see new errors popup and we might catch this problematic bad feed in the act? Hmmm 🧐
#t4h77hq
(#ybzi67q) @slashdot@feeds.twtxt.net I thought Sunday was the hottest day on Earth 🤦♂️ wtf is wrong with Slashdot these days?! 🤣
#fwb5yrq
(#ve43paq) if we can figure out wtf is going on here and my theory is right, we can blacklist that feed, hell even add it to the codebase as an “asshole”.
#tvkftha
(#ve43paq) @stigatle@yarn.stigatle.no The problem is it’ll only cause the attack to stop and error out. It won’t stop your pod from trying to do this over and over again. That’s why I need some help inspecting both your pods for “bad feeds”.
#ocx6sla
(#ve43paq) @abucci@anthony.buc.ci / @stigatle@yarn.stigatle.no Please git pull
, rebuild and redeploy.
There is also a shell script in ./tools
called dump_cache.sh
. Please run this, dump your cache and share it with me. 🙏
#uzeqxfq
(#ve43paq) I’m going to merge this…
#6yy4t6q
(#homd37a) @abucci@anthony.buc.ci Yeah I’ve had to block entire ASN(s) recently myself from bad actors, mostly bad AI bots actually from Facebook and Caude AI
#h2b55bq
(#ve43paq) Or if y’all trust my monkey-ass coding skillz I’ll just merge and you can do a git pull
and rebuild 😅
#5my6z2a
@stigatle@yarn.stigatle.no / @abucci@anthony.buc.ci My current working theory is that there is an asshole out there that has a feed that both your pods are fetching with a multi-GB avatar URL advertised in their feed’s preamble (metadata). I’d love for you both to review this PR, and once merged, re-roll your pods and dump your respective caches and share with me using https://gist.mills.io/
#ve43paq
(#ze3zlba) @stigatle@yarn.stigatle.no I’m wondering whether you’re having the same issue as @abucci@anthony.buc.ci still? mulit-GB yarnd-avatar-*1
files piling up in /tmp/
? 🤔
#3flo6ua
(#uqxxstq) @abucci@anthony.buc.ci So… The only way I see this happening at all is if your pod is fetching feeds which have multi-GB sized avatar(s) in their feed metadata. So the PR I linked earlier will plug that flaw. But now I want to confirm that theory. Can I get you to dump your cache to JSON for me and share it with me?
#essbaxq
(#homd37a) @abucci@anthony.buc.ci Yeah that should be okay, you get so much crap on the web 🤦♂️
#euk2kka
(#uqxxstq) @abucci@anthony.buc.ci sift
is a tool I use for grep/find, etc.
What would you like to know about the files?
Roughly what their contents are. I’ve been reviewing the code paths responsible and have found a flaw that needs to be fixed ASAP.
Here’s the PR: https://git.mills.io/yarnsocial/yarn/pulls/1169
#dp723rq
(#rbzcmka) @abucci@anthony.buc.ci I believe you are correct.
#wwimwva
(#homd37a) @abucci@anthony.buc.ci That’s fucking insane 😱 I know what code-paths is triggering this, but need to confirm a few other things… Some correlation with logs would also help…
#fisjsia
(#uqxxstq) Do you happen to have the activitypub
feature turned on btw? In fact could you just list out what features you have enabled please? 🙏
#mtvjo6q
(#uqxxstq) These should be getting cleaned up, but I’m very concerned about the sizes of these 🤔
#3ejltuq
(#uqxxstq) Hah 😈
prologic@JamessMacStudio
Fri Jul 26 00:22:44
~/Projects/yarnsocial/yarn
(main) 0
$ sift 'yarnd-avatar-*'
internal/utils.go:666: tf, err := receiveFile(res.Body, "yarnd-avatar-*")
@abucci@anthony.buc.ci Don’t suppose you can inspect one of those files could you? Kinda wondering if there’s some other abuse going on here that I need to plug? 🔌
#3bktsva
(#uqxxstq) @abucci@anthony.buc.ci Hmm that’s a bit weird then. Lemme have a poke.
#pypft3q
Hmm remove the cpu limits on this pod, not even sure why I had ‘em set tbh, we decided at my day job that setting cpu limits on containers is a bit of a silly idea too. Anyway, pod should be much snappier now 😅
#s7xvxga
(#rbzcmka) @movq@www.uninformativ.de Oh nothing much 🤣 Just a bunch of folks running really old versions of yarnd
that were susceptible to abuse on the open web 🤣
#srvggpq
(#uqxxstq) Hopefully you should see traffic die off a bit too as the /external
endpoint is no longer externally abusable (get it) without being an authenticated user – which became problematic 🤦♂️ – The web is so fucking hostile 🤬
#hs7bhpq
(#uqxxstq) @abucci@anthony.buc.ci Hopefully it shouldn’t 🤞
#ptf3i5q