Spyke

Replies

Comment on

If the chat leak happened in WW2

This basically happened in Operation Mincemeat

Attached to Martin's body was a briefcase containing secret documents that had been fabricated by the British Security Service. The purpose was to make German intelligence (which was known to have operatives in Huelva) think he had been a courier delivering documents to a British general. The documents were crafted to deceive the Germans into thinking that the British were preparing to invade Greece and Sardinia, rather than Sicily.

Comment on

German police read Signal, Telegram, WhatsApp messages without breaking encryption

Reply in thread

I think you're the only person here so far who read the linked article.

I also found the netzpolitik article that was referenced but not linked to in the original article.

This describes police adding a linked device to a person's WhatsApp account while gathering evidence (translated with Google Translate).

On January 12, 2020, Mr. and Mrs. P. were questioned. During the questioning, they voluntarily handed over the mobile phones they were carrying to the interviewing officers for a brief period so that messages from their daughter contained on the devices could be viewed and, among other things, photographed.

While the photographs were being taken, the computer-based application WhatsApp Web was covertly activated via a website made available online by the Federal Criminal Police Office (BKA), allowing the messages to be read on a BKA computer (sic!). This did not involve any intrusion via a Trojan horse or similar software.

The only link to Signal here is the nation state campaign which used social engineering via a phishing message from 'Signal Support'.

This nation state campaign was originally reported by a researcher at Citizen Lab.

Comment on

Local server can't be seen on Android or iOS, but can on any Linux device

Reply in thread

I was assuming your server and Linux device were plugged in via Ethernet and your mobile devices were using WiFi. Now it sounds like your Linux system may be using the same access point.

It could be something as simple as your browser trying to send the address to a search engine instead of directly looking for the site.

When you're trying to access it on mobile do you manually enter "http://" or "https://"? Those default to ports 80 and 443 respectively.

If you're using nonstandard ports you may need something like "http://192.168.1.42:8080" to use http on port 8080 or any other nonstandard port.

Even if you are 100% sure your server is http or https try the other one to see if your error changes.

You reached the end