bitmask-dev.git/src/leap/bitmask/vpn/helpers/linux, branch 0.10.7 [bitmask-dev] [feat] add support for tcp management in bitmask-root 2018-06-12T20:06:45+00:00 Ruben Pollan meskio@sindominio.net 2018-06-08T18:24:21+00:00 dd9bcff5a2ea0b6e7bda4eeebfe6b74700f8d974 






several fixes for riseupvpn snap
2018-04-11T14:40:10+00:00

Kali Kaneko
kali@leap.se

2018-04-03T00:45:34+00:00

3169015c5f5eaed5f2ad48e486b1fe96e1eb6bbe

- move snap folder to root folder, to allow automated builds
- install only polkit file outside of snap
- change path of bitmask-root accordingly in bitmask
- fix check for polkit file inside snap
- change and document the algorithm for picking bitmask-root in linux
- add LD_LIBRARY_PATH as an environment entry for bitmask-systray





- move snap folder to root folder, to allow automated builds
- install only polkit file outside of snap
- change path of bitmask-root accordingly in bitmask
- fix check for polkit file inside snap
- change and document the algorithm for picking bitmask-root in linux
- add LD_LIBRARY_PATH as an environment entry for bitmask-systray







[pkg] add snap openvpn to bitmask-root
2018-03-02T02:54:18+00:00

Kali Kaneko
kali@leap.se

2018-03-01T12:30:17+00:00

ba2a5cefe99eba802476a57fe282226af5a53a09












[feat] report missing polkit properly from main UI
2018-01-25T00:19:16+00:00

Kali Kaneko
kali@leap.se

2018-01-18T14:37:18+00:00

c3306592fbb54fab0da44a8faaa8a1c6954537fd

also refactor and move polkit_agent so that it does not depend on having
bitmask on the path.





also refactor and move polkit_agent so that it does not depend on having
bitmask on the path.







[feat] hardcode tcp4 in vpn connections
2018-01-25T00:19:11+00:00

Kali Kaneko
kali@leap.se

2018-01-16T22:40:42+00:00

a57c73e33f4937a5050f76ca5224e88801db4afe

for now, we'll be hardcoding tcp as a more reliable alternative, no
matter what the provider announces.

explicitely specifying ipv4 should fix the case in which vpn fails to
start because ipv6 is disabled.

-Resolves: #9181, #9129





for now, we'll be hardcoding tcp as a more reliable alternative, no
matter what the provider announces.

explicitely specifying ipv4 should fix the case in which vpn fails to
start because ipv6 is disabled.

-Resolves: #9181, #9129







[bug] fix the systemctl run
2018-01-16T16:58:59+00:00

Ruben Pollan
meskio@sindominio.net

2018-01-16T16:58:59+00:00

cb1b9e06e3062035df19d9c0812bef7a98bcc51f












[feat] bump bitmask-root version
2018-01-12T10:05:07+00:00

Ruben Pollan
meskio@sindominio.net

2018-01-12T10:05:07+00:00

a351693bc2e13c31352b46d54689618a1606342f












Add Qubes DNS support, fixes
2018-01-12T10:02:58+00:00

Christopher Laprise
tasket@protonmail.com

2017-12-31T12:45:22+00:00

a57a5191216f22718995dad4062243a39fd69626












Add anti-leak rules for qubes-firewall
2018-01-12T10:01:21+00:00

Christopher Laprise
tasket@protonmail.com

2017-12-30T20:36:49+00:00

4da63fae464086d786eaf67d9effdb70d8131a18












[bug] fix issues with dns resolution with systemd-resolved
2018-01-09T21:10:53+00:00

Ruben Pollan
meskio@sindominio.net

2018-01-09T19:49:17+00:00

799f16d85e569755dc7284a4f3d44878b4116d47

In ubuntu 17.10 some changes with systemd-resolved broke our firewall,
blocking all DNS queries. The masquerade rules in the firewall, that
are used to rewrite the source IP address of the DNS queries, were
wrongly modifying the queries to systemd-resolved.

Let's apply masquerade only to the packets addressed to the nameserver.

- Resolves: #9137





In ubuntu 17.10 some changes with systemd-resolved broke our firewall,
blocking all DNS queries. The masquerade rules in the firewall, that
are used to rewrite the source IP address of the DNS queries, were
wrongly modifying the queries to systemd-resolved.

Let's apply masquerade only to the packets addressed to the nameserver.

- Resolves: #9137