Package Details: mullvad-vpn-bin 2024.2-1

Git Clone URL: https://aur.archlinux.org/mullvad-vpn-bin.git (read-only, click to copy)
Package Base: mullvad-vpn-bin
Description: The Mullvad VPN client app for desktop
Upstream URL: https://www.mullvad.net
Licenses: GPL-3.0-or-later
Conflicts: mullvad-vpn
Provides: mullvad-vpn
Submitter: yochananmarqos
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 97
Popularity: 5.65
First Submitted: 2019-11-20 18:07 (UTC)
Last Updated: 2024-04-29 15:33 (UTC)

Pinned Comments

yochananmarqos commented on 2020-04-07 17:37 (UTC)

This package will verify the signature of the source package. The Mullvad code signing key is available here and instructions are here.

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

yochananmarqos commented on 2022-08-27 17:53 (UTC)

@kaulfield: Mullvad bundles libwg, there is no need for wireguard-tools.

kaulfield commented on 2022-08-27 17:46 (UTC) (edited on 2022-08-27 17:46 (UTC) by kaulfield)

This dependency is necessary to connect through wireguard wireguard-tools. Add it please!

madskjeldgaard commented on 2022-05-07 17:42 (UTC)

Is anyone else having trouble with journalctl -f being spammed by this ? Every second or so mullvad posts mullvad-daemon[571]: [mullvad_daemon::management_interface][DEBUG] get_tunnel_state to the log and it makes it difficult to read.

yochananmarqos commented on 2022-03-01 15:42 (UTC)

@askreceive: This is exactly the same version as mullvad-vpn. The pkgrel is unrelated.

yochananmarqos commented on 2021-10-26 23:22 (UTC)

@XenGi: I suppose I should have specifically mentioned I am indeed aware of Arch's package guidelines and principles and normally follow them. What don't you get about what I said? I wasn't making a point, just stating a reason for why I'm doing it this way. It's that simple.

XenGi commented on 2021-10-26 23:10 (UTC)

@yochananmarqos Why should the AUR not follow the same behavior that Arch packages have? I don't get your point. The upstream is not a package but a software. That's two different things. The software should behave exactly as upstream intented but the package should behave like the distro intended. That behavior is pretty much what makes a distro stand out.

« First ‹ Previous 1 2 3 4 5 Next › Last »