It does not return an error. It just set's a boolean. The interface
and the Bitmask3 implementation was changed.

Multiple log levels are supported and can be set via env variable (LOG_LEVEL)
- trace (LOG_LEVEL=TRACE)
- debug (LOG_LEVEL=DEBUG)
- everything else: INFO

updates the changelog

filepath.Join is portable as in it uses the correct
path separator based on the host os whereas path.Join
doesnot

more explaination at: https://stackoverflow.com/questions/39181790/whats-the-difference-between-path-path-filepath-packages-in-go

this fixes a hang in the UI when using the obfs4 transport

fixes #760

Pea Nut authored 11 months ago and Kali Kaneko committed 11 months ago

This commit removed the fallback codepath with the static ip. Discussion in #768

The hardcoded ip was also used for the Snowflake path. I removed it from there and use the DNS hostname. Therefore, the certificate pinning is gone and the SystemPool is used as default. I tested the snowflake setup and it worked.

jkito authored 11 months ago and jkito committed 11 months ago

in preparation of implementing Bitmask interface for
v5 api, the v3 implementation in the  bitmask/legacy
package is renamed to Bitmask3

Pea Nut authored 1 year ago and jkito committed 11 months ago

this extracts the interface implementation code from the vpn
package as preparation for implementing the interface for v5
api of menshen

Pea Nut authored 1 year ago and jkito committed 11 months ago

- vendor.conf now has a default api version:
    - apiVersion = 3 is set for all current providers
- provider.py (called during `make vendor`) now supports api version
  and writes it to providers.json
- the desktop client logs the used api version. Currently v5 is not yet implement.
  This is just the preparation for it
- this is only a temporary solution. In the future, we want to get the
  api version during runtime by parsing $api/provider.json

Pea Nut authored 1 year ago and jkito committed 11 months ago

bitmask.go will be used in the future for the Bitmask5 implementation

Pea Nut authored 1 year ago and jkito committed 11 months ago

Then we can call it later from Bitmask3 and Bitmask5 without having the
code duplicated.

Pea Nut authored 1 year ago and jkito committed 11 months ago

It is only used in the backend package

Pea Nut authored 1 year ago and jkito committed 11 months ago

Using the alias bitmaskAutostart because there is an existing varable
autostart

fixes #786

the tasks are now handled by the post-install.go program the
plist template is in the program source code

the python script needed python to be installed on the user's machine
to be able to successfully install

this is changed to use a statically compiled go binary for performing
the post-install tasks

fixes #775

jkito authored 1 year ago and jkito committed 1 year ago

uses customTheme.iconSplash instead of the static
icon-shield image specific to riseup

the debian source archive name contains the
version of only the upstream source the part
after the last '-' is ommitted if it contains

e.g: source-version: 0.24.03-rc.1-1-ga34h566
     archive-version: 0.24.03-rc.1-1
     archive-name: bitmask-vpn_0.24.03-rc.1-1.orig.tar.gz

python3 is now more likely to be found instead of python, although
macos doesn't ship python pre-installed, we should try to remove
python dependency from the installers

without this the new bitmask-vpn connection/disconnect icons
width becomes larger and overflows beyond the parent container

this currently points to the demo instance of lillypad
going forward this'll be the flavor of the desktop app
that leap team is going to maintain and test