Tootfinder

Opt-in global Mastodon full text search. Join the index!

@wyliesau@noauthority.social
2024-04-01 19:19:59

Disclaimer, THIS IS NOT A JOKE.
This is the PM of Scottland, Pakistani Humza Yousa.
“JK Rowling could be arrested in Scotland for making a series of posts misgendering transgender women, under a newly-enacted hate crime law, a politician in the UK has warned.”
This is insane !!!

@wyliesau@noauthority.social
2024-04-01 19:19:59

Disclaimer, THIS IS NOT A JOKE.
This is the PM of Scottland, Pakistani Humza Yousa.
“JK Rowling could be arrested in Scotland for making a series of posts misgendering transgender women, under a newly-enacted hate crime law, a politician in the UK has warned.”
This is insane !!!

@Techmeme@techhub.social
2024-03-28 21:31:02

Scammers are using sample videos of influencers with modest social media presence to create AI deepfake ads that often push offensive products and ideas (Washington Post)
washingtonpost.com/technology/

@Mediagazer@mstdn.social
2024-03-28 21:45:39

Scammers are using sample videos of influencers with modest social media presence to create AI deepfake ads that often push offensive products and ideas (Washington Post)
washingtonpost.com/technology/

@spamless@mastodon.social
2024-03-28 17:55:16

This story details a valid cause for alarm with deep fakes and identity theft (without, apparently, recourse).
But I'm posting mainly to shake my head at the unintended pun with "bad actors" in the part I put in the screenshot.
"Women’s faces stolen for AI ads selling ED pills and praising Putin" - The Washington Post

The pertinent paragraph runs:

"Because it’s simpler and cheaper to base fake videos on real content, bad actors are scooping up videos on social media that match the demographic of a sales pitch, leading to what experts predict will be an explosion of ads made with stolen identities."
@servelan@newsie.social
2024-04-23 16:52:00

👍 New federal rule bars #transgender school bathroom bans, but it likely isn’t the final word
What to know about new federal rule that blocks transgender school bathroom bans | AP News

@keithwilson@fediphilosophy.org
2024-03-21 15:37:30

When I used ‘Leo Varadker is the Taoiseach’ as an example of a contingent proposition in my lecture the other week, I didn’t realise it would be false before the end of the course!
The same happened with Theresa May when I taught this course a few years ago. I’m now considering putting money on Donald Trump disproving the law of self-identity! 😆 #philosophy

@spamless@mastodon.social
2024-03-28 17:55:16

This story details a valid cause for alarm with deep fakes and identity theft (without, apparently, recourse).
But I'm posting mainly to shake my head at the unintended pun with "bad actors" in the part I put in the screenshot.
"Women’s faces stolen for AI ads selling ED pills and praising Putin" - The Washington Post

The pertinent paragraph runs:

"Because it’s simpler and cheaper to base fake videos on real content, bad actors are scooping up videos on social media that match the demographic of a sales pitch, leading to what experts predict will be an explosion of ads made with stolen identities."
@bthalpin@mastodon.social
2024-02-08 15:37:09

irishtimes.com/crime-law/court

@rene_mobile@infosec.exchange
2024-03-30 21:58:50

My current take on the #xz situation, not having read the actual source backdoor commits yet (thanks a lot #Github for hiding the evidence at this point...) besides reading what others have written about it (cf. #rustlang for such central library dependencies would maybe (really big maybe) have made it a bit harder to push a backdoor like this because - if and only if the safety features are used idiomatically in an open source project - reasonably looking code is (a bit?) more limited in the sneaky behavior it could include. We should still very much use those languages over C/C for infrastructure code because the much larger class of unintentional bugs is significantly mitigated, but I believe (without data to back it up) that even such "bugdoor" type changes will be harder to execute. However, given the sophistication in this case, it may not have helped at all. The attacker(s) have shown to be clever enough.
6. Sandboxing library code may have helped - as the attacker(s) explicitly disabled e.g. landlock, that might already have had some impact. We should create better tooling to make it much easier to link to infrastructure libraries in a sandboxed way (although that will have performance implications in many cases).
7. Automatic reproducible builds verification would have mitigated this particular vector of backdoor distribution, and the Debian team seems to be using the reproducibility advances of the last decade to verify/rebuild the build servers. We should build library and infrastructure code in a fully reproducible manner *and* automatically verify it, e.g. with added transparency logs for both source and binary artefacts. In general, it does however not prevent this kind of supply chain attack that directly targets source code at the "leaf" projects in Git commits.
8. Verifying the real-life identity of contributors to open source projects is hard and a difficult trade-off. Something similar to the #Debian #OpenPGP #web-of-trust would potentially have mitigated this style of attack somewhat, but with a different trade-off. We might have to think much harder about trust in individual accounts, and for some projects requiring a link to a real-world country-issued ID document may be the right balance (for others it wouldn't work). That is neither an easy nor a quick path, though. Also note that sophisticated nation state attackers will probably not have a problem procuring "good" fake IDs. It might still raise the bar, though.
9. What happened here seems clearly criminal - at least under my IANAL naive understanding of EU criminal law. There was clear intent to cause harm, and that makes the specific method less important. The legal system should also be able to help in mitigating supply chain attacks; not in preventing them, but in making them more costly if attackers can be tracked down (this is difficult in itself, see point 8) and face risk of punishment after the fact.
H/T @… @… @… @… @…

@servelan@newsie.social
2024-03-11 23:26:27

😜 From the guy with the 'never back down' PAC:
DeSantis guts "Don't Say Gay" law in deal with LGBTQ advocates - National Zero
nationalzero.com/2024/03/11/de

@arXiv_condmatsoft_bot@mastoxiv.page
2024-02-27 08:34:13

This arxiv.org/abs/2311.00414 has been replaced.
initial toot: mastoxiv.page/@arXi…

@rene_mobile@infosec.exchange
2024-03-30 21:58:50

My current take on the #xz situation, not having read the actual source backdoor commits yet (thanks a lot #Github for hiding the evidence at this point...) besides reading what others have written about it (cf. #rustlang for such central library dependencies would maybe (really big maybe) have made it a bit harder to push a backdoor like this because - if and only if the safety features are used idiomatically in an open source project - reasonably looking code is (a bit?) more limited in the sneaky behavior it could include. We should still very much use those languages over C/C for infrastructure code because the much larger class of unintentional bugs is significantly mitigated, but I believe (without data to back it up) that even such "bugdoor" type changes will be harder to execute. However, given the sophistication in this case, it may not have helped at all. The attacker(s) have shown to be clever enough.
6. Sandboxing library code may have helped - as the attacker(s) explicitly disabled e.g. landlock, that might already have had some impact. We should create better tooling to make it much easier to link to infrastructure libraries in a sandboxed way (although that will have performance implications in many cases).
7. Automatic reproducible builds verification would have mitigated this particular vector of backdoor distribution, and the Debian team seems to be using the reproducibility advances of the last decade to verify/rebuild the build servers. We should build library and infrastructure code in a fully reproducible manner *and* automatically verify it, e.g. with added transparency logs for both source and binary artefacts. In general, it does however not prevent this kind of supply chain attack that directly targets source code at the "leaf" projects in Git commits.
8. Verifying the real-life identity of contributors to open source projects is hard and a difficult trade-off. Something similar to the #Debian #OpenPGP #web-of-trust would potentially have mitigated this style of attack somewhat, but with a different trade-off. We might have to think much harder about trust in individual accounts, and for some projects requiring a link to a real-world country-issued ID document may be the right balance (for others it wouldn't work). That is neither an easy nor a quick path, though. Also note that sophisticated nation state attackers will probably not have a problem procuring "good" fake IDs. It might still raise the bar, though.
9. What happened here seems clearly criminal - at least under my IANAL naive understanding of EU criminal law. There was clear intent to cause harm, and that makes the specific method less important. The legal system should also be able to help in mitigating supply chain attacks; not in preventing them, but in making them more costly if attackers can be tracked down (this is difficult in itself, see point 8) and face risk of punishment after the fact.
H/T @… @… @… @… @…

@cheryanne@aus.social
2024-03-13 06:00:36

F! It!
Great Australian Pods Podcast Directory: #GreatAusPods

F! It! 
Screenshot of the podcast listing on the Great Australian Pods website