WebRTC leak?

[galaczi]

I think the fingerprint-suite should handle any WebRTC leak, but it doesn't. Testing with a new Playwright project, WebRTC successfully leaks my real IP. I could not find any mention in the docs that this needs special setup. Am I missing something?

[janbuchar]

Hello, and thanks for your interest in Crawlee! I don't think this is relevant to the fingerprint suite, it feels like a responsibility of the PlaywrightCrawler to me. In any way, masking the actual client IP address would be tricky in WebRTC - the protocol requires opening a direct network connection between the client and the server, which cannot be done without knowing each other's IP addresses. Possibly a proxy could help here, but to my best knowledge, HTTP proxies usually don't proxy WebRTC.

[galaczi]

Hi @janbuchar, the reason I thought the fingerprint-suite fixes it is this commit:

apify/fingerprint-suite#141

[janbuchar]

Oh, I see! Well, the option to block WebRTC like this is opt-in, so you need to turn it on. Off the top of my head, I'm not sure how you'd do that for PlaywrightCrawler. Can you help us out @barjin?

[galaczi]

I think it should be like this, but typescript complains, so it's probably not exposed to crawlee.

    browserPoolOptions: {
      fingerprintOptions: {
        fingerprintGeneratorOptions: {
          mockWebRTC: true
        }
      }
    },

Edit: seems to work for blocking WebRTC, it's just Typescript doesn't know about it.

[janbuchar]

Huh. Could you make an issue so that we can fix the types to match... the reality?

[barjin]

Indeed, it feels weird to redefine the FingerprintOptions interface in Crawlee - especially if the options are passed straight to the underlying FingerprintGenerator instance. Simply reusing the interface exported from fingerprint-generator should work (hopefully it won't be breaking).