1890? Are we sure about the implementation year?
might be it be 1980?
12 publicly visible posts • joined 18 Apr 2011
I always find error messages like this in the wild really interesting. It's an opportunity to peak behind the curtain and see what goes into these devices, without needing to hack one open your self. It's amazing what a system can tell you about itself just by looking at what they cough up when they're dying - and if your headgear is "of the darker hue" then this is information that you didn't know before without needing to do anything illegal to get access to it.
I found a similar ATM at my local Morrisons supermarket and it's interesting to see how much of the internal infrastructure is (or appears to be) USB based - even the alarm module in that example was usb based.
Way back in the mists of time, my colleague and mentor was issued a desktop computer - laptops were reserved for management types - so he made the best of a bad situation and made a large fabric bag by which to carry his desktop. He used to occasionally work from home or other sites, so you often see him struggling to carry a CRT monitor with this large (i think it was purple) fabric bag slung over his arm.
When they eventually relented and got him a laptop, it was knocked off his desk by his dog and the screen broke - I think he still used a CRT - great guy.
But... I saw amazon at steelcon... last year - they were giving out webcam lens covers. Shirley they weren't just paying lip service to the importance of security on a consumer product. I mean the cynical amongst us might think that a lens cover plastered with the amazon logo is treating the symptom, and pushing an amazon logo in front of eyeballs - even when the laptop is switched off... As I said - that's what cynical people might think.
many moons ago i used to work PC support, and we had a particular range of PC's in the estate - the Mitsubishi VS550 - there was apricot involvement also - all i know was that someone thought these were a suitable replacement for the aging IBM model 50's that they had.
And they were a massive improvement.
Right until they stopped working. After extensive analysis (not by me i hasten to add - I wasn't that clever to figure out what was happening) it was found that the heat dispersal for the CPU was inefficient and cause the CPU over time to ease itself out of it's socket.
Our solution... switch of PC, lift PC 2-3 inches off desk. Drop. The inertia tended to force the chips back in to the sockets enough to let it carry on for a while.
Thumbs up because.... eyyyyyy
The issue here is a Microsoft issue. I mean....it really is, that's why they're releasing a patch for the 0 day vulnerability on their code. The permanent solution doesn't give a fully working ado.net solution back, but at least if someone posts to your website now, they won't be able to potentially break it for everyone.
Command line is good though cos you can at least cut and paste those lines to accomplish something. Think of it like administrative fuzzy felt.
Dear Mr AC...you know what? I'm with the other AC. Read the advisory, and after tge paragraph which describes the type of error, and yes I'd agree that it *could* affect python or ruby or any other server side language, the issue here is that *is* affecting asp.net due to:
"...the way that ADO.NET processes values in an ADO.NET form post, causing hash collisions."
This isn't about ruby, or python, or anything else but ADO.NET.
So, as these projects haven't used Microsoft code for their hash table implementation, then I would suggest that such projects ad ruby and python are not affected by this microsoft code...of course they may have other problems, but the joy of FLOSS us that anyone - even you - can take a look at the code to make sure that the same problem doesn't occur there...now if we could only get a look at the code to see the mistake Microsoft made we could confirm whether the open source code made the same mistakes.