| 2019-04-16 16:03:11 |
Dan Streetman |
bug |
|
|
added bug |
| 2020-02-12 17:59:58 |
Dan Streetman |
description |
login_with() forces a browser window to open, which may not always be what the end-user wants to do. For example on a remote system, a user may want to hand-copy the auth url to open on their local system, instead of having a console browser opened. |
login_with() forces a browser window to open, which may not always be what the end-user wants to do. For example on a remote system, a user may want to hand-copy the auth url to open on their local system, instead of having a console browser opened.
Also when running under sudo, popping up a new browser as the root user is almost certainly not a good thing to do. In fact, chromium/chrome refuses to do so, and prints:
[162589:162589:0212/125610.703398:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
which (if running on graphical system) results in a pop-up showing the error:
"Failed to execute default Web Browser."
"Input/Output error." |
|
| 2020-02-22 17:59:39 |
Dan Streetman |
summary |
login_with forces opening of browser |
login_with should not popup browser under sudo |
|
| 2020-02-22 18:00:19 |
Dan Streetman |
description |
login_with() forces a browser window to open, which may not always be what the end-user wants to do. For example on a remote system, a user may want to hand-copy the auth url to open on their local system, instead of having a console browser opened.
Also when running under sudo, popping up a new browser as the root user is almost certainly not a good thing to do. In fact, chromium/chrome refuses to do so, and prints:
[162589:162589:0212/125610.703398:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
which (if running on graphical system) results in a pop-up showing the error:
"Failed to execute default Web Browser."
"Input/Output error." |
When running under sudo, popping up a new browser as the root user is almost certainly not a good thing to do. In fact, chromium/chrome refuses to do so, and prints:
[162589:162589:0212/125610.703398:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
which (if running on graphical system) results in a pop-up showing the error:
"Failed to execute default Web Browser."
"Input/Output error." |
|
| 2020-02-22 18:04:06 |
Dan Streetman |
description |
When running under sudo, popping up a new browser as the root user is almost certainly not a good thing to do. In fact, chromium/chrome refuses to do so, and prints:
[162589:162589:0212/125610.703398:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
which (if running on graphical system) results in a pop-up showing the error:
"Failed to execute default Web Browser."
"Input/Output error." |
When running under sudo, popping up a new browser as the root user is almost certainly not a good thing to do. In fact, chromium/chrome refuses to do so, and prints:
[162589:162589:0212/125610.703398:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
which (if running on graphical system) results in a pop-up showing the error:
"Failed to execute default Web Browser."
"Input/Output error."
Additionally, similar to bug 1862948, opening a browser under sudo will save any cookies or other browser data as the sudo'ed user (i.e. root, usually) instead of the calling user. This is unlikely to be what the user actually wants, and can be confusing on any system with shared root access, where user "B" may have a browser pop-up automatically log them in as user "A" and/or prefill the wrong login information. |
|
| 2020-02-22 18:53:35 |
Dan Streetman |
branch linked |
|
lp:~ddstreet/launchpadlib/nosudo |
|
| 2020-04-14 11:34:16 |
Colin Watson |
launchpadlib: importance |
Undecided |
High |
|
| 2020-04-14 11:34:16 |
Colin Watson |
launchpadlib: status |
New |
Fix Released |
|
| 2020-04-14 11:34:16 |
Colin Watson |
launchpadlib: milestone |
|
1.10.11 |
|
| 2020-04-14 11:34:16 |
Colin Watson |
launchpadlib: assignee |
|
Dan Streetman (ddstreet) |
|
