digicat@infosec.pubM to

blueteamsec@infosec.pubEnglish · 2 days ago

LinageOS December 2025 security issues - The project had a security problem - project private keys were visible in a publicly visible online git repository.

2

10

LinageOS December 2025 security issues - The project had a security problem - project private keys were visible in a publicly visible online git repository.

digicat@infosec.pubM to

blueteamsec@infosec.pubEnglish · 2 days ago

2

December 2025 security issues

Contribute to lineageos4microg/l4m-wiki development by creating an account on GitHub.

You must log in or register to comment.

Chat

tuxec@infosec.pub
link
fedilink
English
arrow-up
1·
2 days ago
This says a lot about their devs and the security guardrails (not) implemented at their end.
bennypl@infosec.pub
link
fedilink
English
arrow-up
1·
1 day ago
This is why Grapheme os is the way.

blueteamsec@infosec.pub

blueteamsec@infosec.pub

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !blueteamsec@infosec.pub

For [Blue|Purple] Teams in Cyber Defence - covering discovery, detection, response, threat intelligence, malware, offensive tradecraft and tooling, deception, reverse engineering etc.

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

15 users / day
120 users / week
168 users / month
799 users / 6 months
1 local subscriber
651 subscribers
2.51K Posts
175 Comments
Modlog

mods:
digicat@infosec.pub