| Age | Commit message (Collapse) | Author |
|---|
|
polkit doesn't work inside docker.
|
|
also refactor and move polkit_agent so that it does not depend on having
bitmask on the path.
|
|
we make a distinction between the system-wide bitmask-root, which should
be placed there by the maintainers of whatever packages your
distribution uses, and the bitmask-root that is placed by the bundles
(using polkit).
since the bundles copying over the helper from user-writeable folders
is a potential attack vector, we prefer to use the package's version if
present.
also, if we cannot find either, we abort the launching of the VPN. we've
discussed that this might move to the service initialization instead,
but I think the cases in which this is needed should be rare.
I fix also a corner-case in which we were using getcwd() at import time.
if you execute code and then remove the installation path, this will
raise a traceback in bitmaskctl. I think it's nicer to catch the error
properly when starting.
|
|
|
|
Check it before starting the vpn.
- Resolves: #8895
|
|
- Related: #9012
|
|
|
|
Better psutil than ps+grep.
|
|
|
|
|
|
|
|
this commit is porting the polkit launcher from the legacy bitmask
client. if no polkit authentication agent is running, it will try to run
one that is found in the system.
- Resolves: #8836
|
|
|
|
The bundled version of bitmask is unable to find the bitmask_helpers
binary. Let's include it as part of the frozen binary generated by
pyinstaller.
- Resolves: #8862
|
|
I changed most of the logger statements to use a class attribute, in
this way it's easier to identify which class it's logging them.
in some cases I leave a module-level logger, when we're either using
functions or when the module it's too small.
at the same time I did a general review and cleanup of the logging
statements.
|
|
|
|
|
|
|
|
|
|
|
|
non functional at the moment, but started doing some cleanup
|
