On Mon, Mar 19, 2018 at 08:50:50AM -0400, Chris Laprise wrote: > On 03/19/2018 04:32 AM, [email protected] wrote: > > Hello, > > > > I'm trying make set up vpn with bitmask application. > > > > I tried install bitmask to debian template. > > > > have done steps listed on bitmask site as below in termainal: > > > > sudo apt install leap-archive-keyring > > sudo sh -c 'echo "deb http://deb.leap.se/client release stretch" > > > /etc/apt/sources.list.d/bitmask.list' > > sudo apt update && sudo apt install bitmask > > > > But there is info as below > > > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > bitmask : Depends: bitmask-core but it is not going to be installed > > Depends: bitmask-qt but it is not going to be installed > > Depends: bitmask-vpn but it is not going to be installed > > Depends: bitmask-mail but it is not going to be installed > > E: Unable to correct problems, you have held broken packages. > > > > How can I resolve this problem? Any advices? > > > > Hi, > > I'm getting an authentication error when I try to install 'bitmask' with > apt: > > > WARNING: The following packages cannot be authenticated! > > python-leap-common python-sqlcipher soledad-common soledad-client > > bitmask-core bitmask-js > > bitmask-qt bitmask-vpn bitmask-mail bitmask > > > You should probably report the problem to the leap-discuss list. Their > bitmask repository may currently be in a transitional state; I know they > were planning a new release with Qubes support I contributed. > > The current release of the standalone bundle can be downloaded here: > https://dl.bitmask.net/client/linux/ > > Note the current release v0.10.2 doesn't have Qubes proxyVM support. This > means if you run it in a proxyVM some firewall protections won't be in > effect, but it should still work. The latest release candidate v0.10.3rc1 > does have the Qubes proxyVM support. > > Another difference between the current release and the release candidate is > that the former has been signed and can be manually verified with gpg. >
There does seem to be something amiss with the repo - I imported the signing key but still get a GPG error with invalid signature. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20180319220302.s7d2et6wedj337nz%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
