Rick's b.log - entry 2018/01/03

The Big Red Button

Instead, we begin the year with Trump actually managing to outdo his usual level of bullshit. Yes, I said a rude word. You will too when I quote:

Yes.

The so-called "leader of the free world" really did just compare the size of his supposed Red Button.

To Mister (I'm not prefixing your name with "President") Trump: GROW UP YOU PETULANT INFANT.

To Kim Jong Un: This will be what Trump and his crowd would refer to as "alternative truths". The fact is, unless Trump threw a tantrum on his first day in office, there is no such thing as a red button (and if he threw a tantrum and they gave him a red button, it isn't connected to anything more important than a coffee maker).
I think it was Nixon that started the idea of a crazy person with their finger on the button ready to launch a nuclear strike (and worryingly, it was he who was the supposed madman). It took on a life of its own through the Cold War, and now stands as a cross between a trope and an urban legend, the idea that the US President has a big red button on his desk, and whacking it hard will end the world.

Think about Trump.
Now think about him again.
That's all you need to know to understand why there is no button, and it isn't up to the whim of a deranged individual obsessed with size to prod his "bigger" button.

There is a briefcase that is carried around in proximity to the President at all times. For some reason, it is referred to as a "football". It's a radio system, with codes and stuff. It needs to be authorised by a code that is known only to the President.
That's where the good news ends. The President can launch a nuclear strike. By himself. On his whims. At a moment's notice. You can understand the logic of this if you recall the Cold War. When Russia could have attacked America with a serious amount of weaponry, the first bombs would fall in something like ten minutes. There would be no time to get chiefs of staff together, to talk to congress. It would all be over and America a wasteland before everybody could be gathered together, never mind decide upon a response.
But nowadays? Putting all of that power in the hands of a person such as the current President is reckless. Scary reckless.
There is some hope. The president does not carry the "football", it is one of his military aides. One would hope that these aides would be patriotic enough that if their commander in chief decided to launch an unprovoked nuclear attack (even towards North Korea - does anybody think China and Russia wouldn't retaliate?), that they would put "America first" and stick a bullet in the brain of the guy about to start a nuclear holocaust because he is worried about how big his penis button is.

One final thing - it is known that the recent leadership of North Korea have been of small stature. What will it be tomorrow? My daddy is bigger than your daddy?

Way to go, Intel!

Hard details are scarce at this point, but it appears that data from speculative execution is loaded into the cache. The instruction will likely then abort (as user mode programs are not supposed to access kernel level data), however that data remains in the cache and can be picked up.

What this means is that everybody is rushing to tweak their operating systems to work around this problem.
But, and this is enormous, switching contexts around syscalls is expensive. Some benchmarks available show something that suffers badly is PostgreSQL SELECT 1, the best case is 17% slower, worst case is 23%. On the bright side, it does not appear to affect gaming in any noticeable way. On the cloudy side, it may hit emulation fairly hard, and this might include virtual machines. Time will tell if services like AWS and web hosts suffer.

There is a lot of FUD around this. I've seen it mentioned at the problem also affects ARM processors, yet AMD processors providing the x86-64 instructions are not affected...?

I don't know. What I do know is that Intel have made a lot of cock-ups recently.

More information on TheRegister

HP Instant Ink

On January 1st, I installed the cartridges. It took a couple of minutes for the printer to authorise the cartridges and register their use. Once that was done, the printer did a quick head clean, and then printed out the alignment sheet.

I don't recall if it was the website or the booklet with the Instant Ink, but they said "don't worry if the cartridges are a little bit bigger, they'll fit". Well, damn, they weren't kidding:

And just to maximise the creepy, just after I'd installed them, a message appeared on my PC:

Super Luna

Here's a long exposure I took. Looks like any normal daytime photo with slightly wonky colour balance...until you notice the stars.

Your comments:

Please note that while I check this page every so often, I am not able to control what users write; therefore I disclaim all liability for unpleasant and/or infringing and/or defamatory material. Undesired content will be removed as soon as it is noticed. By leaving a comment, you agree not to post material that is illegal or in bad taste, and you should be aware that the time and your IP address are both recorded, should it be necessary to find out who you are. Oh, and don't bother trying to inline HTML. I'm not that stupid! ☺ ADDING COMMENTS DOES NOT WORK IF READING TRANSLATED VERSIONS.
 
You can now follow comment additions with the comment RSS feed. This is distinct from the b.log RSS feed, so you can subscribe to one or both as you wish.

Rick, 4th January 2018, 09:10

Yes, numerous ARM cores are affected in various ways. It looks like it is due to data leakage to the cache from speculative/out of order execution.  https://developer.arm.com/support/security-update  The main difference appears to be down to how much of a penalty mitigating this will incur...

Add a comment (v0.11) [help?] . . . try the comment feed!
		Your name
		Your email	(optional)
		Validation	Are you real? Please type 06521 backwards.
		Your comment