111–120 of 476 posts
Earlier quoted context omitted.
As in a manhole cover in a street for maintenance.
Yes, yes. Seems like an outdated term. Downvotes accepted.
Manhole is, indeed, an outdated term. Generally the preferred term is "Maintenance Hole". Still abbreviated MH, and people in the field use all three interchangeably (much like metric/imperial).
Source: I work with storm/sanitary/electrical maintenance holes.
At a previous workplace we had a few places in the code which used the word backdoor. It was not an actual backdoor though, but merely a debugging server that could be enabled and allowed you to inspect internal state during runtime. At some point I removed the word backdoor, fearing it would get to a customer or during an audit someone would misunderstand. :|
Frankly I don't think Intel's track record affords them the privilege of having good faith be assumed with something like this.
> If you find password protected zips in the release the password is probably either "Intel123" or "intel123". This was not set by me or my source, this is how it was aquired from Intel. Can't say I'm surprised, people are lazy. Another large tech company I used to work for commonly used an only-slightly more complex password. But it was never changed, so people who had left the team still could have access to things…
Intel denies it was hacked: https://twitter.com/TheRegister/status/1291461942624677889
Earlier quoted context omitted.
I can agree with that with the caveat that "enabled" has to be at either something that only the user can do. If it requires that the customer intentionally run a debug build, that's fine; if it can be toggled on without their knowledge, then it's a problem.
It was disabled by default, and could only be enabled using environment variables. Even when enabled, the whole thing ran in Docker and the socket was bound to loopback, so you could only connect to it from within the container. When the intention is a debugging server, making it exposed to the world is a mistake and a security vulnerability. At that point it is effectively a backdoor, but the difference between a hi…
At a previous workplace we had a few places in the code which used the word backdoor. It was not an actual backdoor though, but merely a debugging server that could be enabled and allowed you to inspect internal state during runtime. At some point I removed the word backdoor, fearing it would get to a customer or during an audit someone would misunderstand. :|
A manufacturer wanted to upgrade one of their equipment lines to be more modern. The developers of the original product, both hardware and software, were no longer with the company. Since they just wanted to add some new features on top and present a better rack-based interface to the user, they decided to build a bigger box, put one of the old devices inside the box, then put a modern PC in there, and just link the…
Earlier quoted context omitted.
Which country laws does apply? Is it really illegal to share this in the whole world? Im not so sure about that.
Intel is an American company; so wherever there is an extradition treaty with the USA and where there are also similar laws.
Earlier quoted context omitted.
Which country laws does apply? Is it really illegal to share this in the whole world? Im not so sure about that.
Intel is an American company; so wherever there is an extradition treaty with the USA and where there are also similar laws.