The previous DMCA threats are from a company called Cyberlock, I had planned to do a fun little blog post (cause i
What should researchers do when companies make baseless legal threats to maintain their security-through-obscurity?
I was going to dissect the security service for not taking customer data importantly, but the linked articles have no mention of "Microsoft monitoring black-hat sites for employee credentials" at all. I don't know where the Slashdot article editor got that.
Advanced threat analytics is from Microsoft's acquision of Aorato last November, who's main product protected against internal threats by warning of non-typical login activity:
A compromised employee's mobile device exposes the organization, through Active Directory, to identity theft and information disclosure.
Monitoring and auditing solutions (such as tracking changes) of Active Directory cannot correlate information between entity behavior and information residing in Active Directory.
15.04 ships with KDE Plasma 5.2. In order to get 5.3 and future KDE updates, you will need to add the backports ppa repository:
sudo add-apt-repository ppa:kubuntu-ppa/backports
sudo apt-get update && sudo apt-get dist-upgrade
I have a 1993 Taurus. It doesn't require a code reader as it is before the mandated OBD port in 1996, but still has sequential electronic fuel injection and an engine management computer that can be chipped and tweeked. How to get the codes? Put a paperclip between two pins of the underhood diagnostic connector, and count the flashes on the dash to get the codes. It has engine-running tests to diagnose sensors and report weak cylinders. The number of times it has seen a mechanic other than me in the twelve years I've owned it? Zero. It also doesn't spy on me with black box data available for insurance companies and law enforcement.
Regarding the original premise that people be able to modify their software, most flash MCUs made these days have a secure or protected mode: the firmware goes in to the chip, but doesn't come back out. There is no external flash EEPROM or data bus to access or hack, and the only way you would be able to update it is to understand the entire MCU and how every one of its data ports and D/A and A/D IO is used by the manufacturer and the specs for those sensor lines, and write a completely new firmware. We are talking minutia like knowing whether individual data lines are set high or low by the internal configurable pull-up circuits.
They currently are offering this service to 25 ZIP codes - likely those directly surrounding a distribution center. However, there are several logistical factors that just seem to make this unworkable to scale:
1. If I place seven orders a day, I alone have monopolized a driver and his vehicle for an entire work shift if the distribution center is 30 minutes away from me. That's the labor cost and vehicle cost for an entire day that my orders must pay for in "shipping".
2. 30 minutes one way trip is optimistic, I live in the 25th largest city, and it took me 80 minutes round trip just to go to a Radio Shack that had an item I needed in stock, 1/3 of the metro area away.
3. Even if there were distribution centers where every Walmart has a store in the US and they had a fleet the size of FedEx themselves (FedEx even just does a daily route), can they really keep the kind of items everywhere that I would order? Today, soldering iron tips, NiMH battery sub-c cells with solder tabs, replacement cherry mx keycaps, other days Loc-tite blue adhesive, 55" 4K TV, USB floppy drive, heat pump valve, that Spiderman comic from 1993...let alone that 80% of the items on Amazon are single-item-only things from marketplace sellers, very few of whom ship their entire inventory to Amazon for safe-keeping.
The challenges here are likely why they are thinking WAY out of the box, like delivery drones.
I specified and owned an EISA system, a rare 486-50 (not double-clocked DX2), with 16MB memory, $4000 or so spent.
EISA is a very odd beast, if you recall the original ISA bus that had jumpers you had to set on each card to non-conflicting IRQ, Address IO, and DMA values, then you will see the "brilliance" of EISA, which had a floppy disk config program for every card you bought to set the bus values. Seeing anyone that still has the matching and required EISA setup disks for their hardware is going to be the rare thing to find.
This is also completely Microsoft's fault. In Vista they decided to kiss the ass of big media companies in order to play Blu-Ray content, which required encrypted end-to-end data transport, mandating the rewriting of the driver stack for everything from video and sound cards to imaging devices and audio mixing. They should have just given them the finger.
What Microsoft didn't have to do was just completely discard gameport support. Microsoft blatantly removed the code to support 15 pin gameports from the OS. In Vista 32 bit, it could be partially put back by driver hacks of old dlls, but that hack was made impossible in win7. You could literally buy joysticks at the same CompUSA that would not work on the Vista shitboxes they were selling.