#[tantek]snarfed, this quote is for you (and everything about security on silos vs "indieweb")
#[tantek]"In the aftermath of the compromise, Popov said that PHP maintainers have concluded that their standalone Git infrastructure is an unnecessary security risk. As a result, they will discontinue the git.php.net server and make GitHub the official source for PHP repositories. Going forward, all PHP source code changes will be made directly to GitHub rather than to git.php.net."
#[snarfed]obviously not the state of affairs we want! or that we should settle for.
#[tantek]but it is the current state of (git) affairs, and we should acknowledge that
#[snarfed]but it’s ok to accept that computer security these days is hopelessly complicated, and attackers often very advanced, and in many instances self hosting things is harder to secure than thoughtfully using silos as infrastructure where appropriate
#aaronpkdo keep in mind that someone's own git repo is unlikely to be as big a target as PHP
#[tantek]snarfed indeed, you've made similar points in the past and I figured would appreciate this datapoint of confirmation
#[snarfed]true, somewhat. but attacks are very automated and widely applied
#[tantek]aaronpk, I see it the other way, because PHP uses/used git, any exploits that were developed for that could also be re-used on someone's personal git repo
#[snarfed]they could, but aaronpk’s point is that they likely wouldn’t, since a small personal repo isn’t a very interesting or valuable target
#[tantek]the person using an attack tool is not the same as the person developing it for a high value target
#[tantek]this is why there are such things as "script kiddies", they use attack scripts, not develop them
#[snarfed]oh i was definitely talking about the attack user, not the developer
#[snarfed]yes i’m very well aware. they’re who i meant. both by interesting/valuable and by automated
#[tantek]point being, once a high value target has incentivized a dev to create a tool, others will use it in random places purely for mischief
#[snarfed]semi-random, yes. and also widely, sometimes for the same, more often now for profit. domain hijacking for SEO, etc
#[tantek]e.g. for as trivial a reason as having a short twitter handle 😛
#[snarfed]i’m agreeing with both of you 😁 aaronpk historically, you nowadays
#[jgmac1106]I actually took my app down since my last st schools not using it to refactor (then I priced the data storage increase and hid in corner quivering)
#[jgmac1106]Last school year* Started December time, just a constant barrage of Javascript injection automated attacks
#Loqi[Jeremy Keith] The principle of most availability
[scojjac] and [aciccarello] joined the channel
#GWGsebsel: I do. But I write a plugin that can be used on many people's sites. I have to check, but I think I strip JS from content.
#jackythis didn't seem like a vuln of Git but of a home made solution
#jackyif anything, it just seemed like it lacked enough community review to prevent things like this
#jackykinda sad that they decided to just jump ship to GitHub tho
#[tantek]yes sad, but also interesting as a community deciding what was the more sustainable option for them
#[tantek]admintax is a real thing even for such a well established community like PHP
#[tantek]jamietanna[m] did you try checking BarryF's site with IndieWebify.me to see if it identified any errors related to the problems you're seeing with it not showing up in your reader?
leo60228, Kaja_, AkyRhO_, sknebel_, deltab_, globbot, nertzy__ and [Jeff_Hawkins] joined the channel