For the most part it confirms what is already well known in the privacy community:
But the one part I found most notable was that “even a fully unlocked GrapheneOS device is immune from having its data copied”. While they could obviously look at data on the screen of an unlocked device and extract information accessible to the user, it would seem Cellebrite can’t actually get a complete FFS extraction of a GrapheneOS device even with the unlocked phone in their hands. If the team behind GrapheneOS has been able to make their system this resistant to industrial level phone hacking, it is quite the accomplishment for a small non profit and begs the question of why Google don’t implement the same security for Pixels running stock Android OS.
]]>Police forces have been using drones for a while now, but usually on a smaller scale like DJI consumer drones. While these are still quite useful in law enforcement, they are hampered by their short loiter time, and can’t carry as much payload. By contrast, the S-100 can loiter in the air for over 6 hours and can carry a 50kg payload.
]]>“RESCUE” is used when they are on a real emergency callout. Your flight tracking app may display this callsign as SRG
“COASTGUARD” is used for non emergency operations, like a training exercise or a repositioning flight. Your flight tracking app may display this callsign as SRD
The callsign will then be followed by a 3 digit number, which refers to the base that aircraft is operating from. Each Coastguard base has its own number. For example, Prestwick uses 199. So when there’s an emergency one of the fells in the Lake District and they call in SAR support from Prestwick, the heli will deploy with the callsign RESCUE 199.
When you watch OpenADSB long enough you will start seeing times where a Coastguard heli on a training or routine flight gets caled into action. The SRD will suddenly change to SRG along with a drastic change in course and speed.
What implications could this have for anonymity and privacy? Well it has always been known that Tor is not completely foolproof and that a nation state adversary who can see and monitor the entire internet backbone could theoretically carry out timing attacks to deanonymize users. The NSA has had the capability to deanonymize some Tor users, some of the time since at least 2012. The Krone article would suggest that this is now a practical attack even for law enforcement, who are usually considered to have less capabilities than intelligence agencies. However, The Tor Project has published this post in response to the news, which goes into a bit of detail and concludes that the success of the operation was more down to luck and user error. The suspects in this case were apparently using an outdated version of Tor, one that lacks some of the in built protections included in recent versions. This appears to have made them easier to deanonymize.
https://www.flightradar24.com/data/gps-jamming
It works by aircraft measuring the strength and quality of the GPS signals they receive when travelling, and then broadcasting this data which is then picked up by FlightRadars network of receivers and fed into the system. When there is no GPS interference, aircraft will usually get a decent signal. These areas are marked green on the map. If aircraft are getting a very weak signal, or struggling to get one at all, that could suggest there is jamming in the area. It doesn’t mean there definitely is, because there are a number of other reasons why an aircraft might be struggling to get a signal. For example, their equipment could be damaged. But if FlightRadar sees that multiple aircraft in a specific area are all having trouble getting a signal, they mark that area as red as that is more suggestive of jamming rather than faults with the individual aircraft.
]]>Show All Air Ambulances
G-CRWL,G-KRNO,G-TAAS,G-WNAS,G-PICU,G-TCAA,G-NICU,G-CPTZ,G-DAAS,G-DAAN,G-DSAA,G-RESU,G-HEMC,G-EHEM,G-HHEM,G-NHAC,G-NHAD,G-NHAE,G-GWAC,G-HIOW,G-KSST,G-KSSC,G-LNAC,G-KSSA,G-EHMS,G-LNDN,G-MGPS,G-RMAA,G-OMAA,G-HWAA,G-NWAA,G-NWAE,G-NWEM,G-SPHU,G-HEMZ,G-RSCU,G-SCAA,G-EMAA,G-ISAS,G-GSAS,G-SASC,G-SASD,G-TVLY,G-WENU,G-WOBR,G-WROL,G-WASC,G-WLTS,G-YORX,G-YAAA
Show All Police Aircraft
G-POLA,G-POLB,G-POLC,G-POLD,G-POLF,G-POLG,G-POLJ,G-POLH,G-POLX,G-POLV,G-POLW,G-POLZ,G-POLU,G-EMID,G-CPAO,G-NWOI,G-TVHB,G-CPAS,G-DCPB,G-MPSA,G-MPSB,G-MPSC,G-HEOI,G-SUFK,G-POLS
Show All Coastguard Search & Rescue
G-MCGI,G-MCGF,G-MCGE,G-MCGH,G-MCGZ,G-MCGY,G-MCGJ,G-MCGK,G-MCGG,G-MCGL,G-MCGP,G-MCGM,G-MCGS,G-MCGV,G-MCGW,G-MCGU,G-MCGO,G-MCGX,G-MCGR,G-MCGT,G-UASA,G-UASB,G-UASD,G-UASE
There is an Enhanced Secure Erase option that does appear to properly overwrite the data, but this option doesn’t show as being available for many drives. And the PartedMagic interface doesn’t really make that clear, which I think should be fixed. The name Secure Erase clearly suggests that your data will be properly wiped, PartedMagic should put some prominent warnings in the interface to let people know that isn’t the case unless they choose the enhanced option.
The procedure I now recommend for wiping SSD’s and flash memory is nwipe 3(a fork of DBAN/ Darik’s Boot & Nuke). This tool is also available on the PartedMagic live OS. Follow the instructions on the interface carefully, you need to select which drive you want to wipe and be careful you don’t get the wrong one. I have been told that if you start the process without selecting any drive, it will start wiping them all but I have not tested that. Chose the PRNG Stream option as the method, this will overwrite the selected drive with random data. Once that is complete, run the same method again. The reason you should run it twice is because flash memory usually has a bit more space on the drive than advertised. For example a 16GB flash drive might actually have 20GB. A single pass will just write 16GB of random data, leaving a lot of that hidden “overprovisioned” space untouched. Running it twice ensures you wipe the overprovisioned space as well.
I have tested nwipe with a couple of USB flash drives, and could not recover any files once the drive had been overwritten twice, so I think it is a secure enough method.
On magnetic hard drives it’s fine to overwrite data with zeroes, but on SSD and flash memory it is vital that you overwrite with random data instead. Flash storage can detect when it is being told to write a long string of zeros and will often just mark that sector of the drive as being all zero without actually writing the data. This is a feature that helps prolong the life of your drive by avoiding unnecessary write cycles, but it makes secure deletion a little more complicated. But if you overwrite with random data, you don’t get this issue. The data will be properly overwrittenitten and the drive wiped.
To truly remove data from a device, such that it can no longer be recovered, you need to overwrite it, replacing the old data with new data. Below are the procedures I would recommend
| Type Of Device | Procedure | HDD | Download and boot ShredOS on a live USB and run the 3-pass DoD wipe on the HDD |
|---|---|
| SSD | No Longer Recommended See here for why, and an alternative method |
| Android | Factory Reset the device
Set a new 16 character passcode (the longest Android allows) Fill up the device with random data Factory Reset the device. Set a new 16 character passcode and fill it up with random data again Factory reset a third time. At this point, there is virtually no chance of recovering any old data on the device |
| iPhone | To Be Added |
| USB Flash Drive | On Linux, open a terminal and run dd if=/dev/urandom of=/path/to/usb to overwrite the entire USB stick with pseudorandom data. You must run this command twice, in order to be reasonably sure that you've also wiped any overprovisioning space
On Windows, download Eraser and run the 3-pass DoD wipe on any files currently on the USB. Once this is done, run the "Erase unused space" option on the USB. Once completed, run the "Erase unused space" option once more, to account for any overprovisioning space. |
| SD Card | Same process as USB flash drive |
| Individual Files | On a HDD use the secure erase feature on Eraser or CCleaner to overwrite specific files. Use the 3-pass wipe, or optionally more passes if you like. On an SSD you can't reliably erase individual files. The only way to be sure you've properly deleted something is to wipe the entire drive but that is often not practical. What you should do is use Full Disk Encryption on the drive before storing any sensitive data on it, then it's protected by the encryption. I recommend Truecrypt (Version 7.1a - Download here) for full disk encryption if you are using Windows, and LUKS for Linux systems. |
“You’ve already opened Chrome 30 times this month. Click here to subscribe to our Web Browser Ultimate Plan which will let you open your browser as many times as you like. Just $19.99 a month, reduced to $14.99 today!”
It sounds ridiculous now but give it 10 years and I wouldn’t be at all surprised
]]>