search

beakerbrowser / beaker

An experimental peer-to-peer Web browser
https://beakerbrowser.com/
MIT License
6.75k stars 545 forks source link

Error: "This browser or app may not be secure" asks to use different browser!! #1912

Open MrLuxuri opened 3 years ago

MrLuxuri commented 3 years ago

I recently moved from firefox to beaker browser and have been in the process of making it my daily browser but this really makes things hard for me. Screen Shot 2021-02-26 at 2 19 28 PM Please do fix this:)

pfrazee commented 3 years ago

Yeah this is a known issue and we're not sure how to get around it.

On Fri, Feb 26, 2021 at 1:21 PM Archit notifications@github.com wrote:

I recently moved from firefox to beaker browser and have been in the process of making it my daily browser but this really makes things hard for me. [image: Screen Shot 2021-02-26 at 2 19 28 PM] https://user-images.githubusercontent.com/71905307/109345270-deb9f880-783d-11eb-95ba-736f3998d829.png Please do fix this:)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/beakerbrowser/beaker/issues/1912, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJWCU4JRR42WNPOC477ZH3TA7YEDANCNFSM4YI7FWLA .

MrLuxuri commented 3 years ago

Yeah this is a known issue and we're not sure how to get around it. …

But google services is widely used and it is very important, users will need this to work properly to use the browser, what User Agent are you guys using? Maybe using Firefox, or chrome's user agent will work out?

00-000 commented 3 years ago

In 2019 Google caused the same problem for most independent browsers, and the Firefox user agent specific worked.

freedomtrain commented 3 years ago

Has this issue been resolved ?

poeck commented 3 years ago

Quick Solution

app.userAgentFallback = "Chrome";
app.on("ready", ()=>{
    session.defaultSession.setUserAgent("Chrome");
}

Source

But

Google restricts Sign In's from non standard browsers for a couple of reasons! A browser running on electron could for example simply have a keylogger installed. That's why google warns developers not to modify their browser's user-agent.

The browser must identify itself clearly in the User-Agent when connecting to accounts.google.com. The browser must not use another browser's User-Agent string, such as Chrome or Firefox on that host.

Source