PSA: we're aware that Signal is down for some people. This appears to be related to a major AWS outage. Stand by.
Bluharmonishing
Haptishing
Jpgishing
:)
Just want these to exist outside my phone, amazing concert!
- This example covers image file formats, so other file formats will have other nuances. For instance, the "Convert Image" approach on macOS won't work for a PDF document.
- The image itself might contain personal information that is not related to the metadata (photos, specific signs, etc.)
Please keep in mind that:
- There are many edge cases, but if you create the images, it should be ok with the information on this thread.
- In Windows/Linux, removing metadata reliably might require extra tools if you want a Graphical User Interface (GUI)
However, if using exiftool is difficult (or just annoying), there are other ways. For instance, in macOS, you can right-click the file, go to "Quick Actions", and select "Convert Image" to create a new version of the file; just uncheck the option "Preserve Metadata" and you should be good to go :)
Ok, so back to the original file: if you are comfortable enough to run tools on the command line, exiftool, the one we used to check the existing metadata, can also remove it in a new version of the image. In this case by running "exiftool -all= not_made_by_me.png"
PAUSE! Before we get too stressed, let's say something actually good and helpful: if we send the picture over Signal or WhatsApp, this data will be deleted (mostly because the platform creates its own version of the picture, hopefully optimized). This example is for the same image on Signal
Now, if we use a tool for extracting the metadata in a more professional way (exiftool for the curious), we get this on the file (spoiler: 😐 You can see my name, that I used Canva to create the image with documents and user id, and some other weird fields that I couldn't find much about 🤔)
Let's take this image above (not_made_by_me.png), usual guidance says to right-click and then select Properties/Get Info to check the available metadata. Here is what it looks like for Windows, Mac, and Linux (Ubuntu in this case):
Let's talk metadata: Today, a friend of mine in a risky environment asked me how to make sure an image they designed is not traceable back to them, since it's been a while since the last time I checked "deeply", it was time for a refresh!!
- This example covers image file formats, so other file formats will have other nuances. For instance, the "Convert Image" approach on macOS won't work for a PDF document.
- The image itself might contain personal information that is not related to the metadata (photos, specific signs, etc.)
Please keep in mind that:
- There are many edge cases, but if you create the images, it should be ok with the information on this thread.
- In Windows/Linux, removing metadata reliably might require extra tools if you want a Graphical User Interface (GUI)
However, if using exiftool is difficult (or just annoying), there are other ways. For instance, in macOS, you can right-click the file, go to "Quick Actions", and select "Convert Image" to create a new version of the file; just uncheck the option "Preserve Metadata" and you should be good to go :)
Ok, so back to the original file: if you are comfortable enough to run tools on the command line, exiftool, the one we used to check the existing metadata, can also remove it in a new version of the image. In this case by running "exiftool -all= not_made_by_me.png"
PAUSE! Before we get too stressed, let's say something actually good and helpful: if we send the picture over Signal or WhatsApp, this data will be deleted (mostly because the platform creates its own version of the picture, hopefully optimized). This example is for the same image on Signal
Now, if we use a tool for extracting the metadata in a more professional way (exiftool for the curious), we get this on the file (spoiler: 😐 You can see my name, that I used Canva to create the image with documents and user id, and some other weird fields that I couldn't find much about 🤔)
Let's take this image above (not_made_by_me.png), usual guidance says to right-click and then select Properties/Get Info to check the available metadata. Here how it looks like for Windows, Mac, and Linux (Ubuntu in this case):
That said, when you try to disable any of these things, it offers you to disable the Advanced Protection mode altogether and it is not hard: biometrics and a restart that can be done later if you want. So it is promising for sure, but as it is implemented not bulletproof for physical access cases.
Enabling Android Advanced Protection on a Pixel from the stable update: very easy to activate, and I haven't noticed any usage problems or incompatibilities. The intrusion logging isn't there yet (so alert on that one), and I couldn't disable Play Protect or enable 2G networks as advertised.
IIRC they work but with currents that are below specification, so they do the job but can break easier or they need to be put in gentler settings (not too cold) for them to work
According to some of my electrical engineering teachers, it was known that people in my home country tied one cable to the tower's structure and another to a metal bar stuck in the ground some meters away to power refrigerators and lights effectively stealing power without major issues.
“The truth is that a tattoo identifying Tren de Aragua does not exist,” she told me. “Tren de Aragua does not use any tattoos as a form of gang identification; no Venezuelan gang does.”
Starting today, our chapter in Venezuela will be operating in exile. The growing threat to its members has made the situation too dangerous to remain in the country.
Our statement here ⬇️
I’ve posted a detailed explanation of why the claimed ESP32 Bluetooth chip “backdoor” is not a backdoor. It’s just a poor security practice, which is found in other Bluetooth chips by vendors like Broadcom, Cypress, and Texas Instruments too. https://darkmentor.com/blog/esp32_non-backdoor/
Yea this would be physical
