Space and Naval Warfare Systems Command (SPAWAR, in other words "Space War") had a problem fulfilling The Next Generation Enterprise Network (NGEN) contract? I think the Navy Trekkies are in control of the acronym office!
And also RSA token, car keys, home keys, work keys. Looking for two mini-screwdrivers to round it out.
Their products are uniformly flimsy, ugly and poorly constructed. It's truly more expensive to support these cheap things than to pay the difference for something of average or good quality.
THIS THIS THIS. I'm typing on an Acer laptop right now. The price was good, the specs were good, and it sure looks nice... But the touchpad is way too sensitive, the keyboard is flimsy, and the screws holding it together started falling out the moment I took it out of the box.
I've got a mobile phone too, same thing, the engineering and quality control is quite simply bad.
because you should never sign a cert that has an expiration date later that that of the signing cert !
The tablet is doubtless cool! Restricting oneself to available hardware, the doctor could have a mike inside the suit, and the assistant could then easily take dictation outside.
To put things into perspective, how well would Napoleon do against full might of the 2015 US Military? And that's only 200 years of technology.
No need to go to 200 years. Pitch 1945 US armed forces against anything > 30 years prior.
I've run without AdBlock since forever, because hey the guys running the content get money that way, and sometimes the ads are useful, sometimes I click, and sometimes I've even bought... but just this week I encountered an ad by Essilor that just wouldn't shut up, with the useless AdChoices button but without the X to get rid of it. I closed the page, installed Adblock, went back to finish the page. Three days later I am definitely not missing all those ads!
The better system is called capabilities. Think "everything is a file descriptor". You want to create a file, you get a file descriptor. You want to run most programs, you give them read-write scratch space, a place to find common library routines (that don't carry any rights by themselves), and probably a read-write access to some graphical interface window. You're a browser, your user clicks on a java applet? You download the applet into a descriptor from your scratch space, you run it, giving it a read-write descriptor to some user interface sub-window created from your own window, read-write to a descriptor of some scratch space created from you scratch space, and read-execute of some descriptor containing a library, probably the same one you got from your parent. You have a video with a proprietary codec? You run the proprietary program as above with read-only to the video. You're a word processor? You get a RW descriptor to the file you're editing, and a call-back to your parent if your user requests an "open file" dialog, which returns a RW (or maybe RO) descriptor to the file the user indicated. See a pattern? See KeyKOS, which actually worked for years, and followers EROS, CapROS, Coyotos, which none got to to any useful status. There was a guy who rewrote libc on these principles, IIUC so that you'd only have to change file-handling logic in classical programs and recompile. But I get the impression that most people working on these things are security and OS researchers in academia (sincerely sorry if someone feels insulted, I'm not helping out and if you weren't working on it I wouldn't even know about these things), and not people saying OK, I have a generous budget, I have excellent developers and excellent team leads and stellar project managers, now I want a timeline and then a product.
For other non-OS projects see Plash, Capsicum, Tahoe-LAFS, E-Lang, CapDesk...
An awful lot of them probably died in the process... and 'dead men tell no tales'.
TFA says 320000 imates from the local concentration camp, and the Russians did discover the plant... just not all of it.
After actually RTFA (at the Mirror), part of the facility was discovered and cannibalized by the Russians, but they missed a bit (a bit: 75 acres is 300 000 sqm, 3.27 million sqft...)
I'll invent a tool that allows you to kill people via a phone line. I could see a really HUGE market for something like this.
There might be a volume filter, but I wonder what would happen with an air horn. I suppose they have earphones, so if you start off speaking really quietly...
sounds a lot like The Swarm by Frank Schatzing (excellent book...)
At least they will have done it on purpose and not while researching a windshield for an airplane . . . Splat.
16 megabytes of RAM...
It was 640 kB, and Bill Gates denies having said it
Granted it's not good if the IDs are easy to guess, nor if the list of IDs+names gets out, but as long as you're not using the ID to authenticate people, only to identify them, it shouldn't be a terrible problem. Think ID=username, not password. What they say about the credentials seems a bit more worrying, but we'd need a lot more info here . . .