I wasn't saying it was a sane way to do it, just the easiest. I could also see it turning into a nationalism issue -- "The West is unfairly attacking native CAs." -- as impetus to try to convince people to manually trust and/or renew certs with them.
Less difficult. Setting up a private CA means you have to be the CA, and vet and/or create a cert for every wosign/startcom site that people visit. One could trust them just enough depending on how heavily they depend on affected sites. I personally would rather whitelist sites as-needed, but can see why some admins would go the easier route.
Quite a bit, actually. It's why high end telescope CCDs do similar things. A high ISO means you're ramping up the gain, so the bits of random noise get amplified too. Cooling it means you're getting rid of one of the more significant sources.
You'd need a lot more current in order to cause horrible consequences for an airplane. Lots of redundant systems, lots of testing for electromagnetic tolerance.
Even a non-bulk attack can be done pretty cheaply these days. Places like seeed will do boards for a buck a piece if your design's small enough and you get a ten pack. Doing smt work is honestly more bark than bite compared to pth; a $20 toaster oven will work Well Enough for something like this.
A zero-day key wouldn't have hardware costs that would be significantly different from an HID key. A lot of microcontrollers will gladly announce themselves to be whatever sort of device class you want them to be, and which vendor and device IDs to use. Also, if you're worried about bulk, putting an LED or something that flashes and looks pretty would also lower peoples' guards as to why it's so big. USB hacking is an area where there are wide open fields to play with.
Yes, some people won't give back. However, a project like llvm/clang, most people do give back because sharing is cool, and also it makes their job easier because they don't have to repatch for every new version of the compiler. Sony's team developing the Playstation 4 wished at times they could use newer versions of llvm/clang for their software, but couldn't because their version had so many patches [1]. Because of this, after the PS4 was released, Sony developers sent a bunch of patches upstream, and work pretty closely with the rest of the developers. Some bits and pieces may not get merged upstream, but that's the same for any project, GPL or not.
Air mail. These were the days before good roads crossed the country, and where even an automotive trip was an Adventure which would take weeks. Horseback, you're going slow enough that you'd be able to see much smaller signs, and would be on a pretty well-trod path.
Shortly thereafter, though, a few things happened that made the arrows pretty obsolete. Mapping of course, was a big one; you could now navigate a lot more reliably through unknown territory. More importantly, a network of radio beacons was set up. Charts had lists of radio beacons, with their frequencies. Pilots could tune in to hear them repeatedly chirp their identification in morse code, and use radio direction finders to set their heading accordingly.
There's one other feature that was developed in that time period which also made pilots' navigation job a lot easier. The federal highway system meant that there were good, very visible, roads, serving as routing beacons in their own way. Pilots would, and still do for a lot of general aviation planes, route close to highways, because they're also a very obvious landmark that carves a path through the country.
A chip with a design more suitable for embedding in a device. After you make the initial outlay, SMD components become much more easy to deal with than pth, for example.
I'd say the Teensy is in the Arduino++ camp there. It uses the same libraries, etc, just has more power processing, a pretty nice price, and some interface bits and pieces that are very nice, like being able to act as a usb device and host. A lot of hardware, I'd argue is better to be treated as a library -- there are libraries and hardware that have definite feature sets, some of which overlap, that allows you to choose the best tool for the job.
What you're describing is managed hosting. In order to do it, you either have to oversubscribe like hell, and deal with latency, or pay for wide open swaths of server. Pick your poison.
Yep. It's good old fashioned webhosting. Drop your files in the amazon equivalent of ~/public-html/ . If it serves your needs, it's not a bad thing, but it's hardly revolutionary.
It seems like it. The woman who the Post is mentioning, Kathy Glatter, has a rather white-washed google presence, marred only by the article on her behavior, which quite likely is rather linked at the moment. http://www.davisenterprise.com/local-news/north-davis-parent...
In addition to people for whom the vaccine doesn't work, there are certain groups, like those with compromised immune systems, and infants, that rely on herd immunity. There's also the disruption from mass absences if an outbreak does happen. The teacher has to spend time to reteach things because of absences, to the detriment of everyone involved.
In order for a medication to even begin human testing, you need to show that you've done a ton of lab work to show that a medication works, and that the side effect profile is probably minimal. So, by the time it's offered to you, the risks of the drug having disarming side effects, or of causing you to join the caudal class, are pretty damn minimal.
Support costs for shutting down the average user are higher than the costs of bandwidth. Telling someone that their internet was shut off because their device was used in a botnet would lead to very long support calls and escalations.
The problem needs fixed from both ends. Developers that write and maintain programs with bad defaults should be named and shamed as well. Their software has a security flaw that allows these problems to be exploited. Back in the 90s, the default configuration for most mail servers was to allow relaying from all and sundry, until the spam problem made people realize that an open relay was a bad thing that would be abused by malicious actors. Saying developers' time shouldn't be "wasted" on this is like saying automakers' time shouldn't be wasted on airbags and people should just drive better.
Copy/paste was the real problem, not init scripts. Look at the init scripts of FreeBSD some time. They're short, well-documented, and built around reusable components. SysV init was a mess because init scripts became a cargo cult of copy-paste, rather than actually using all the capabilities that were available.
Pages like this make me really convinced I need to print up frame cards for the various lenses I use. I use a lot of vintage glass when I'm shooting that obviously won't have Exif data. It would be useful for later browsing to know at a glance whether I was shooting with a Jupiter 3 or a Pentax Super Takumar.
A lot of more recent Arduinos use more sophisticated cores than the AVR. There are several models that use ARM cores, there are a few that use x86 variants, etc. One of the advantages I can see with the Arduino infrastructure is that the libraries are fairly reasonably cross-platform, so you can use them on multiple projects which use different micros without having to rewrite a bunch of code.
There are other JVMs that already do AOT compilation. This just brings an AOT compilation option to Java. It also looks like the contained file will include both the compiled version and the normal bytecode, so that the code can be recompiled if/when necessary.
FreeBSD's sound drivers include software mixing, so that if there are multiple things that want to use a sound card, they don't block each other. Alsa's sound channels are blocking, which means that only one program at a time can use the sound device, which is what causes the entire tower atop it to form.
There are a number of places where PDF has advantages that HTML, etc can't match. For forms, the PDF spec has electronic signatures, which means that you can sign legal documents without having to find a fax machine, or mail things back and forth. For print documents, it can do things like multiple column text in a sensible manner, across page breaks. As a general document format, it allows you to actually describe paper sizes, etc, so you can email someone a document that looks like it will when it's finalized. For archival, it means you can, without a bunch of hacks, create searchable documents of old, scanned in content. So things like electronics datasheets are searchable, and still retain the formatting of the originals. PDF continues to exist because there are so very many places that the alternatives are an even bigger pain in the ass, fix those, and then you can start to get rid of pdf.
Relying on libpulse is just relying on another layer of the shit sandwich that is the Linux audio stack. Windows and OS X, when they've revamped their audio APIs, the older stuff tends to still work, and tends to be able to take advantage of some of the improvements. Linux audio, on the other hand, is a layer of pulseaudio atop a layer of alsa's userspace components, which is atop a layer of alsa's driverspace components. Instead of people doing things right, and fixing the interfaces that already existed, they added more and more layers of latency-inducing, cpu consuming crap.
PulseAudio is cross-platform.. For FreeBSD in general, it uses further development of Open Sound drivers, which have things like in-driver mixing that Linux drivers under Alsa even lack.
No, this is not per the documentation, this is per the physical specifications, the circuitry that needs to be in place, the support that needs to be in each component. The Management Engine is not as all-seeing as you make it out to be.
Interdiction could happen with open source hardware too. Swipe the SoC, and no one would be the wiser. Given everything that has to be in place for vPro/the ME to work, looking at the pcb would give enough information to tell exactly how much, if any, information it could steal, if all the malicious items were in place. All of which could be easily undone by reflashing it, because the write line on the bios is not controlled by the CPU. A lot of steps have to be done, physically and in software in order to exploit it, and that exploit would melt away on the first bios flash. I'd be much more concerned about the security of the software running on the system than any theoretical hack on the ME.
Only for the m7, because they enable vPro there. For the m3, vPro's not available, so the management engine won't be able to talk to the network card. Alternatively, you could just plug in your own USB wifi device, because it definitely wouldn't have the components for vPro to work.