![]() |
"Mark Zuckerberg clarifies who can access WhatsApp messages." |
There have been many discussions over time about whether someone else can read WhatsApp messages. This issue has now been clarified by Meta's CEO, Mark Zuckerberg.
Recently, Meta's CEO, Mark Zuckerberg, admitted that U.S. authorities, including the CIA, can remotely log into users' devices and read their messages. They are capable of bypassing the platform's end-to-end encryption.
Last Friday (January 10), Mark Zuckerberg explained the issue during a conversation on the Joe Rogan Experience podcast. He mentioned that while WhatsApp's encryption prevents the content of messages from being viewed, it does not protect against physical access to the user's phone.
This comment came in response to a question from Rogan regarding the attempt to arrange an interview between Russian President Vladimir Putin and Tucker Carlson. In February of last year, after three years of unsuccessful attempts, Carlson succeeded in speaking with Putin, and during that conversation, he blamed U.S. authorities, specifically the NSA and CIA, for hindering his efforts.
Carlson claimed that agencies had tapped into his messages and emails to spy on him. Additionally, they had leaked his intentions to the media, which allegedly intimidated Moscow from speaking with him. Rogan asked Zuckerberg to explain how this could happen despite the encryption system in place to secure messages.
Regarding encryption, Zuckerberg said, "The good thing about encryption is that it's designed in such a way that even the company running the service can't see it. So, if you're using WhatsApp, Meta's servers won't be able to see the content of the message."
He further stated, "Even if someone hacks Meta's database, they will not be able to access users' private texts."
According to him, the Signal messaging app, which Carlson used, employs the same encryption, so the same rules apply. However, he noted that encryption does not prevent law enforcement agencies from viewing messages stored on a device.
0 Comments