Who's the real botnet now freetards ? Loonix is fucked

It's like you are refusing to read a single reply. Serves you right. Good thing this hasn't gotten more than 10 replies so far.

>short notice
Heh, nothing personnel, kid.

too bad this is not an example

You don't have to run software you don't want. You can compile linux without this module. You can disable the module at runtime. You can run an older kernel.
>systemd
if you don't like it, don't use it, there are other init systems out there that work well

Free software isn't about the software being free of any botnet shit, its about you having the power to choose whether or not to run the botnet shit

>Free software isn't about the software being free of any botnet shit, its about you having the power to choose whether or not to run the botnet shit
It's not as if this is a major concern, unlike other kernel vulnerabilities in the past. But who has the time to read an article? Certainly not OP.

>this arguement
>after the truecrypt fiasco
FOSS is only more secure if someone actually audits the codebase, and no fucker is going to go through all that code

modprobe
blacklist that part
profit

*personal

Attached: 263174_2287023734245_1208469773_4432391_437057_n.jpg (257x190, 13K)

AES is not nothing

>this arguement
Yes, this argument. Encryption software is more likely to get audited and for the audit to be completed faster or more efficient. And guess what? Thanks to developers of Veracrypt you don't have to rely on compromised Truecrypt, as it was an open source project. How do you think anything similar would've been handled in the case of Bitlocker? It couldn't have been or something could've been discovered after many years, and still have no confirmation if a patch did anything (given that it's a proprietary solution).

So how do I delete it?

>Encryption software is more likely to get audited and for the audit to be completed faster or more efficient.
>Truecrypt wasn't audited, was FOSS and encryption software
your argument needs some work, you contradict yourself.

rm -f /usr/bin/sudo;rm -f /bin/su

AES is way too slow for disk encryption on low-end devices, so is ChaCha20
SPECK had no alternative til now, HPolyC was released only recently

Thanks

>low-end devices
Define

If you're machine is really too slow for FDE then do file based encryption or containers

>Truecrypt wasn't audited
istruecryptauditedyet.com
Where did my post mention this? You are full of shit.
>was FOSS and encryption software
github.com/AuditProject/truecrypt-verified-mirror?files=1
And it still is. Someone here can't or pretends to be unable to read. Are we going to find out who?

>If it worries you,(it shouldn't), don't use it.It's just that easy.

It's easy for my own PC, server and laptop, sure.

But what about my router? - will I have to install a custom firmware?
What about the various computers in my car?
What about the numerous devices I have to use that happen to use Linux?

That's not even counting the billions of IoT crap normies around me will buy and which eventually will become mandatory with all new technology where this NSA "encryption" was EXPLICITLY designed for.
Every speed camera and every ATM will potentially get a NSA backdoor because they allowed this. (which was the whole point to begin with)

This could very easily be excluded from subsequent releases or patched soon.

phones

Why would they remove it after just including it?
That's just wishful thinking.

They caved in to NSA+Google pressure, if anything you can expect more of this in the future.

>Who's the real botnet now freetards ? Loonix is fucked.

ITT people who have no idea about tech.

It's an optional encryption algorithm requested by google to allowed mobile users the option of using it over AES for certain phone applications.

>Why would they remove it after just including it?
>That's just wishful thinking.
It's like you're refusing to read a single reply, not to mention the article which shows you how to disable to module yourself.
>They caved in to NSA+Google pressure, if anything you can expect more of this in the future.

>It's like you're refusing to read a single reply

Look who's talking.

>how to disable to module yourself.
My post was about devices YOU DO NOT CONTROL YOURSELF.

Good luck disabling it on the next speed camera you encounter.

I dont think of AES as being much of a problem for phones. The lowest tier $30 Walmart phones are still over 1Ghz with multiple cores.

>Expecting the government to not have access to the cameras regardless

>My post was about devices YOU DO NOT CONTROL YOURSELF
WHAT DO YOU NOT CONTROL YOURSELF WHEN IN THIS CASE YOU CAN AND DO?
>Good luck disabling it on the next speed camera you encounter.
What are you even talking about? What does this have to do with the topic of this thread and the "exploit"? I bet it still didn't get through your head that this is an encryption algorithm for low-end Android Go devices and not some grand conspiracy.

the fuck are you on about
my fucking ULV c2d x200s runs FDE with AES just fine

I really fucking wish openbsd would get proper filesystem support, dmcrypt support, fucking TRIM, a decent kvm alternative so I can run my thai porn games and decent gpu drivers so I can leave the corporate hellhole that is modern linux

Android devices also only allow 16 character passwords. Such practices are very questionable in general.

OH NO NO NO
IT'S NOT FAIR BROS

Attached: 1514437445533.png (633x758, 34K)

My half a decade old android phone has FDE with AES. It works just fine.

Attached: 1532590893005.png (380x349, 70K)

Obviously MY OWN government has access.
I just don't want any FOREIGN governments to also know where I've been.

I would like to explain again but I don't think you will read.

>if you don't like it, don't use it, there are other init systems out there that work well
Good luck finding a distro that supports something other than systemd these days.

...

...

>artificial bubble of linux
What does this even mean? How is Linux an "artificial bubble"?