One of the most important features that Apple during WWDC21 in June was iCloud+ with iCloud Private Relay, which adds an extra layer of security to enhance privacy while browsing the web. However, according to a Reddit user, the iCloud Private Relay feature is responsible for leaking users' original addresses via WebRTC.
See also: iCloud+: Custom email domain feature available in beta (how to use it)
Of course, most Apple users don't need to worry about this just yet, as iCloud Private Relay is currently only available in the beta version of iOS 15 and will be rolling out to the general public later. However, testers should be aware of the issue so they know the feature isn't working as Apple promised.
Here's what the Reddit user who noticed the issue wrote:
“If you run a test with Private Relay enabled in the Reflexive connectivity step, you will see your address from your ISP. If you connect via VPN or proxy and retry the test, then there is no leak. I have reported this bug to Apple. Just so you know“.
See also: iCloud and WhatsApp: How can they trap you for child pornography?
The user also said that a solution could be to enable “WebRTC Sockets Proxying under Experimental WebKit Features. However, In-App Safari will still display the leaked address even when enabled.”
So, if you're running the latest beta version of Apple's upcoming operating system, iOS 15, you should know that iCloud Private Relay is not working as expected and websites can discover your web address.
Last week, the company said that iCloud Private Relay is officially considered a “beta feature” and that it doesn’t come enabled by default.
See also: Tim Cook: What product does he want to complete before he retires as Apple CEO?
What Apple wrote about iOS 15 beta 7:
“iCloud
New features in iOS & iPadOS 15 beta 7
iCloud Private Relay will be released as a public beta to gather additional feedback and improve website compatibility (82150385)“.
Private Relay is currently in beta. Some websites may have issues (incompatibility).
The Reddit user reported the bug to Apple, and it's likely that the company is working to fix it in future betas.
Source: 9to5mac
