Could what has just happened to the AUR happen to FreeBSD ports?

[tOsYZYny]

Eh, just my 2-cents, but in this day and age, I would think that there is always room for improvement in the CI/CD space. Changes need to be verified before further actions are down, if they fail, stop immediately and raise a red flag. In the context of 400+ packages, perhaps a distributed engine will manage that better.

Another reason to avoid user repositories unless you're actively inspecting what you're getting.

 

[MrBSD]

Eh, just my 2-cents, but in this day and age, I would think that there is always room for improvement in the CI/CD space. Changes need to be verified before further actions are down, if they fail, stop immediately and raise a red flag. In the context of 400+ packages, perhaps a distributed engine will manage that better.

Another reason to avoid user repositories unless you're actively inspecting what you're getting.

Its not 400+ packages. Its almost 2000 packages as of today. AUR is still under attack and number of compromised packages is growing fast and its becoming more sophisticated and hard to find.

 

[mer]

Its not 400+ packages. Its almost 2000 packages as of today. AUR is still under attack and number of compromised packages is growing fast and its becoming more sophisticated and hard to find.

I think, as a cautionary tale, this is a good example of "don't blindly upgrade/update software". But it should give people a reason to think about accepting patches and pull requests (yes, I understand this is more than that).
Tongue in cheek/conspiracy mode:
"This is why you should only use Windows and Government Approved/Controlled applications because we will keep you safe"

To be clear, that was sarcasm (I hope)

 

[tOsYZYny]

I was going to say that perhaps we should only use Apple or Microsoft in the same vein ...

I used 400 as that was what was quoted earlier.

To me, this is no different than a DDoS attack, the platform should provide better tools to mitigate this. While we might be immune now, how long.

As the saying goes, the chain is only as strong as the weakest link.

 

[astyle]

o me, this is no different than a DDoS attack,

Ummm.... a DDOS is an attack from the outside. This "denial of service" happened from within. The attack vector has magnitude and direction, and they both matter. That is the difference (figuring out where the problem originated, outside or inside) that is actually important to understand when deciding if an incident is a DDOS or not. For reference:

https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/ offers a very nice and simple explanation of what a DDOS is. It's pretty safe to assume that if a service disruption does NOT check the boxes as described in that link, it's most likely NOT a DDOS to begin with, and requires very dfferent approaches to problem solving.

 

[mer]

astyle I understand and agree with you, but I think tOsYZYny analogy is not far off. What happened/is happening with AUR results in something similar to a DDoS: loss of the asset. DDoS loss of asset is due to external forces, AUR the loss is due to internal.

I'm not trying to speak for him, but that's how I read post #54. I could be wrong, if so everyone can flog me behind the bikeshed.

 

[MG]

astyle I understand and agree with you, but I think tOsYZYny analogy is not far off. What happened/is happening with AUR results in something similar to a DDoS: loss of the asset. DDoS loss of asset is due to external forces, AUR the loss is due to internal.

I'm not trying to speak for him, but that's how I read post #54. I could be wrong, if so everyone can flog me behind the bikeshed.

I have the suspicion that it's intentional to push for identification facilities around the end-user. Wait for it... They can't verify a user's authenticity without forced centrai supervision. The end user can no longer be root, like on Android and iOS.

 

[tOsYZYny]

I didn't mean it to be literal. I meant that the scope of the attack is large due to how fast AI can generate and obfuscate its tracks that even though this may be surgical now, the sheer volume of it is like a DDoS attack.

In any case, I still suggest that platforms need better tooling around 'security'.

 

[MrBSD]

I think, as a cautionary tale, this is a good example of "don't blindly upgrade/update software". But it should give people a reason to think about accepting patches and pull requests (yes, I understand this is more than that).
Tongue in cheek/conspiracy mode:
"This is why you should only use Windows and Government Approved/Controlled applications because we will keep you safe"

To be clear, that was sarcasm (I hope)

Few years ago on Arch forums i saw several people saying "im not using AUR because its not secure". I read that, an i thought, god what a bunch of idiots. It turned out, those guys were right. And i was the idiot. You cant trust anything or anyone today.

I was going to say that perhaps we should only use Apple or Microsoft in the same vein ...

I used 400 as that was what was quoted earlier.

To me, this is no different than a DDoS attack, the platform should provide better tools to mitigate this. While we might be immune now, how long.

As the saying goes, the chain is only as strong as the weakest link.

The problem is man power.

Ummm.... a DDOS is an attack from the outside. This "denial of service" happened from within. The attack vector has magnitude and direction, and they both matter. That is the difference (figuring out where the problem originated, outside or inside) that is actually important to understand when deciding if an incident is a DDOS or not. For reference:

https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/ offers a very nice and simple explanation of what a DDOS is. It's pretty safe to assume that if a service disruption does NOT check the boxes as described in that link, it's most likely NOT a DDOS to begin with, and requires very dfferent approaches to problem solving.

Speaking of DDoS attacks, both AUR, official arch repositories, along with their website was under heavy DDoS attack 4-5 months ago and it lasted for months. Forum, website, repositories... everything was inaccessible.

I have the suspicion that it's intentional to push for identification facilities around the end-user. Wait for it... They can't verify a user's authenticity without forced centrai suoervision. The end user can no longer be root, like on Android and iOS.

While someone will call you super crazy and paranoid, i think this might be the case. Intentially cause chaos, blame those pesky Russans and Chinise, and then solve the problem with age and identity verification. Very nice.

 

[astyle]

astyle I understand and agree with you, but I think tOsYZYny analogy is not far off. What happened/is happening with AUR results in something similar to a DDoS: loss of the asset. DDoS loss of asset is due to external forces, AUR the loss is due to internal.

I'm not trying to speak for him, but that's how I read post #54. I could be wrong, if so everyone can flog me behind the bikeshed.

Ummm...I think it's kind of important to know when an idea is only half-understood. And in this case, realizing what is a DDoS and what's not, and why that is the case, that makes a difference in problem solving. 50% understanding / correlation / comparison is still a very significant gap. The attack is closer to a Trojan than a DDoS...

 

[MG]

Ummm...I think it's kind of important to know when an idea is only half-understood. And in this case, realizing what is a DDoS and what's not, and why that is the case, that makes a difference in problem solving. 50% understanding / correlation / comparison is still a very significant gap. The attack is closer to a Trojan than a DDoS...

Ddos is distributed overload of a TCP/IP server with (preferably complex) bogus requests. What has this too narrow supply chain as weakness to do with it?

 

[astyle]

Ddos is distributed overload of a TCP/IP server with bogus requests. What has this too narrow supply chain as weakness to do with it?

Ask tOsYZYny to explain...