Is this a common and well-defined term that people use? I've never heard it.
It would appear to me from the context that it means something like "web browser with AI stuff tackled on".
16,731 karma · joined March 7, 2014
Is this a common and well-defined term that people use? I've never heard it.
It would appear to me from the context that it means something like "web browser with AI stuff tackled on".
The whole thing looks like a PR stunt for an Infosec product. Just that they somehow convinced the EU to fund it.
It also should be the central issue - together with the energy/climate impacts - in every debate about AI ethics or AI safety. It's those two things that will harm us most if this hype continues unchecked.
The problem is... it doesn't line up with the facts.
Git has been using SHA-1 hashes for signatures since very early on. It also has claims in its documentation about "cryptographic security". It does not rigorously define what "cryptographic security" means, but plausibly, it should mean using a secure hash function without known weaknesses.
What you're paraphrasing here is the so-called "robustness principle", also known as "Poestel's law". It is an idea from the ancient history of the 1980s and 09s Internet. Today, it's widely understood that it is a misguided idea that has led to protocol ossification and countless security issues.
Honest question:
* Do you understand OS syscalls in detail?
* Do you understand how your BIOS initializes your hardware?
* Do you understand how modern filesystems work?
* Do you understand the finer details of HTTP or TCP?
Because... I don't. But I know enough about them that I'm quite convinced each of them is a lot more difficult to understand than ACME. And all of them and a lot more stuff are required if you want to run a web server.
I mean...
* Github is owned by Microsoft.
* The reason for this are AI crawlers.
* The reason AI crawlers exist in masses is an absurd hype around LLM+AI technology.
* The reason for that is... ChatGPT?
* The main investor of ChatGPT happens to be...?
What exactly are you talking about? It does not sound like it describes the way nuclear power, uranium mining, and nuclear waste storage works.
I mean, sure, there is some impact. Storage media has to be produced. But there's a reason storage is cheap, it's not a whole lot of resources going into it. And hard drives that are idle in some data center without being accessed don't consume a lot of electricity.
There are very real and concerning problems with the environmental impact of IT. But they are primarily found in other areas. Energy consumption is mostly a function of "how much you compute with data", not "how much data you have".
In other words: be concerned about so-called "AI", be concerned about Bitcoin. Don't worry about unused data too much.
I don't see any details there. Is there some link missing here, or is it the wrong link?
I'd be interested to read how your tool found it.
What kind of problem is solved by a fast, hardware-based entropy source? You only need a couple of bytes of entropy to initialize your RNG.
Every OS already has a secure RNG API. That's a solved problem.
Quantum RNGs are gimmicks that are sold as a solution to a security problem. But they don't solve any security problem. There are real security problems with RNGs, but none of them is solved by a Quantum RNG. They usually come down to implementation errors or not using a secure RNG.
Yes, if you mean by "theoretical quantum attacks" the stuff we could run if we had a scalable quantum computer. Those impact public key crypto. They do nothing to impact the security of RNGs.
By choosing OpenOffice, you should be aware that you are at an increased risk for attacks. One of the consistent problems with OpenOffice over the past years has been that they have often not published security fixes for many months, sometimes critical ones, for vulnerabilities that were publicly known.
(Due to the shared codebase, obviously, many security issues affect both LO/OO, yet, with the difference that LO usually fixes them in a timely manner.)
To be clear, I'm not necessarily a fan of DMARC, particularly how it was introduced. But it is very obvious that spammers will eventually do everything to not be flagged as spammers.
What DMARC gives you is that it makes it less likely that your phishing mail will come from contact@yourbank.com. It will rather come from contact@y0urbank.com or some other domain.
How much of an improvement that is and how many people will notice is certainly debatable. But that's what DMARC can give you. Nothing more, nothing less.
It looks into the numbers for the Texas renewable buildout, and there's a very important caveat: the amount of renewables you build is not the relevant metric. Emission reduction is. And Texas does not succeed there.
Nevertheless, it's not exactly how it was pitched. This Microkernel thing always had a "Linux is doing it wrong, we're doing it better" story behind it. They wanted to be a replacement for a general-purpose OS. That cetainly hasn't happened.
That was 20 years ago. As far as I can tell, this has not changed. (Quick googling tells me there appear to be some efforts to build an OS on it, but they all look more like proof of concepts, not like something with real-world use.)
1. It's a very lonely example.
2. It's not clear how big the market is for "you can break encryption from the past, but not current encryption, because once QCs arrive, everyone will obviously move away from QC-breakable encryption". And I'm not aware of any other reasons why factoring large numbers would be useful beyond breaking encryptions.
At the time, the construction of new coal-fired power plants was a controversial topic in many locations in Germany. (Around 30 new coal power plants were planned at times. Some were stopped, but 10 of them were actually build, which is bad enough.) I also tried to raise awareness about this incident in Tennessee, trying to have a look at the environmental issues of coal on a more international level. But it didn't generate much interest.
Climate change. Maybe you've heard of it?
(And it turns out things with LNG ships are much worse than previously believed. They not only emit CO2 - a bit less than traditional bunker fuel, but not much - they also emit methane, and in no small quantities. The LNG industry likes to pretend that these emissions are small and neglegible, but whenever someone goes out and actually measures them, they are substantial.)
First of all, it's quite unlikely that this is going to happen at all. There are no signs of significant weaknesses in SHA-256.
But if it's going to happen, in all likelyhood, you'll get preliminary results long before any actual breakage. (For both MD5 and SHA1, you had around a decade of warnings between "this looks insecure / broken in theory" and "we now have an actual collission".) Anyone paying attention and moving away from algorithms already known to be broken was unaffected by the MD5/SHA1 weaknesses.
Of course, there will be those who will wait until an actual breakage, and a few years more, before they act. (As we've seen particularly with MD5.)
It is always brought forward as an argument when the perceived landuse issue of solar is brought forward. But if you do any serious analysis, the landuse impact of even utility scale solar is so neglegible that it's not an issue to worry about.
If you want to talk about landuse impacts of renewable energy, there's really only one issue to focus on: bioenergy crops. It can be as bad as 30 times less space efficient than generating the same energy with solar photovoltaics.
Talk about using the same space to make food and bioenergy. Use agricultural land for food, and utilize the residuals as good as possible. Stop making biofuels out of food. And treat the space needed for utility-scale solar as what it is: tiny.
(P.S.: If people can make agriphotovoltaics work, I have no issue with that. Great. Even tiny impacts should be reduced if possible. But I have an issue with the way this is discussed, because it makes up a problem with photovoltaics that largely doesn't exist.)
I think I am the "inventor" of the first 64 and 32 byte intro competitions. (Just checked, we ran a 64 byte competition at the 0a000h 2002 and added 32 byte in 2003.) See https://0a000h.de/2002/ and https://0a000h.de/2003/ - releases are on scene.org