A bit later than usual, and perhaps not very exciting this time around, but here are the LSM, SELinux, and audit* highlights from the Linux v6.10 merge window.
I’ve had a few people reach out to me to ask how secure Argos Translate is.
I try to take security seriously; but of course all software has bugs. To my knowledge, to date, no one has found a serious security vulnerability in Argos Translate or LibreTranslate. It’s probably inevitable though that ArgosTranslate/LibreTranslate or one of it’s dependencies will have a security vulnerability at some point.
Do you use the composer audit option in your CI/CD Pipeline and if so how do you use it?
I have implemented it very simple and all security vulnerabilities and abandoned packages must be fixed before the pipeline continues. The reason is that we don’t want this issues in our production code anymore.
'Incredibly disturbing': calls for audit of out-of-home care providers after court hears Aboriginal baby's aunt refused as carer due to same-sex relationship
A bit later than usual due to some personal travel earlier this week (Go Blue!), but here is my write-up on the SELinux and audit highlights from the Linux v6.8 merge window. As a bonus, I'm also going to start including LSM layer highlights as we've got some cool new things starting with Linux v6.8 :)
Цікаво, що деякі з цих IP-адрес мають шкідливі індикатори і б'ються по VirusTotal... Де гарантія того, що через них не пролізе бекдор...? Ми, звичайно, відфільтруємо подібні з'єднання фаєрволом і зашифруємось vpn'ом. А звичайний користувач? У нього усі "брами" відкриті по дефолту...