Forgot your password?
typodupeerror

Comment Re:Bose (Score 1) 32

Their noise cancelling is apparently good. The actual cancelling bit, not the overall sound. But it's also massively over-priced and there are better options, especially when it comes to comfort.

Comment Re:Fatalism (Score 1) 65

All the NIMBYs objecting to solar farms and wind turbines being build on their precious "green belt"... It's all going to die off in the heat and be replaced anyway. That ideal vision of England is dead, literally. It can't survive the heat, and neither can many of the NIMBYs. Tens of thousands of extra deaths this summer, and it's only the start.

Maybe we can turn fatalism into something positive.

Comment Re:PHP (Score 1) 72

What the AI does is not impressive. Finding use-after-free requires you to be competent and wanting to find them. Approaches for finding and avoiding them are well established, the current slop-coders (with or without AI) just do not know or use them. AI is not needed in any way. AI is just the ElCheapo approach when you do not care about finding all of them (due to LLM unreliability).

Comment Re:Unauthorized? (Score 1) 24

By the user against the AI agent? Yes. But online-banking needs authorization by the bank and that involves more than just the act of logging in. It includes tools used, geolocation of login, etc. and does even include what the user does and recent usage history and even things like cards issues, credit rating, etc.

The bank is _not_ talking about the login itself.

Comment It would be interesting to watch form the outside (Score 1) 65

Humans destroying their living conditions on a global scale due to greed, stupidity and lack of caring. How much of the current high-tech civilization will survive? Anything between "almost all" and "nothing" seems to be possible. Will humanity itself survive? Probably. But will it ever be able to go beyond primitive tribes again? Unclear.

Now, being in the midst of it is far less appealing.

Comment Re:Nothingburger (Score 1) 72

I would be wary of that statement. It says "nowhere as easy as log4shell". Log4shell was so easy to attack that it is hard to imagine making it any easier. And second, while the author claims the published exploits do not work against "vanilla PHP", that is a really weak statement and there is no analysis given why they do not work and what is needed in addition.

Comment Re:Reducing Risk (Score 1) 72

At this time, any kind of use after free vulnerability in production code musst be regarded as a sign of gross incompetence. This one seems to have been harder to find or nobody was looking. But still.

Ways to find/avoid: Zeroing pointers on free, "gcc -f analyzer", tests with valgrind (test data needs to trigger at leat a read to free'ed memory), code review, some other tools and less less general ways. The first two are cheap and should be standard. Code review for this problem should be at well.

Zeroing memory on freeing it may or may not do anything. Generally, unless you had secrets in that memory, it will probably not help or only cover part of the possible scenarios. It is also computationally expensive. Hence you should think about it, but doing it generally is probably not the best idea.

Slashdot Top Deals

Don't hit the keys so hard, it hurts.

Working...