Package Details: monkeysphere 0.44-1

Git Clone URL: https://aur.archlinux.org/monkeysphere.git (read-only, click to copy)
Package Base: monkeysphere
Description: Leverage the OpenPGP web of trust for OpenSSH and Web authentication
Upstream URL: http://web.monkeysphere.info/
Licenses: GPL3
Submitter: fauno
Maintainer: svalo
Last Packager: svalo
Votes: 22
Popularity: 0.001578
First Submitted: 2011-01-20 23:39 (UTC)
Last Updated: 2021-10-13 06:55 (UTC)

Latest Comments

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

mhemeryck commented on 2018-10-08 07:56 (UTC)

Tried doing an install via pikaur; got this issue:

+++ /dev/fd/63  2018-10-08 09:51:07.734374988 +0200
@@ -1,5 +1,5 @@
-pub:u:1024:1:0E41076773CB19F7:1538985067:::u:::scSC
-uid:u::::1538985067::E90EC72E68C6C2A0751DADC70F54F60D27B88C3D::monkeymonkey
-sig:!::1:0E41076773CB19F7:1538985067::::monkeymonkey:13x:::::8
-uid:u::::1538985067::8200BD0425CC70C7D698DF3FE412044EAAB83F94::testtest
-sig:!::1:0E41076773CB19F7:1538985067::::monkeymonkey:13x:::::8
+pub:u:1024:1:0E41076773CB19F7:1538985067:::u:::scSC::::::::0
+uid:u::::1538985067::E90EC72E68C6C2A0751DADC70F54F60D27B88C3D::monkeymonkey::::::::::0
+sig:!::1:0E41076773CB19F7:1538985067::::monkeymonkey:13x::85763FA8731311FE9C1EB3710E41076773CB19F7:::8
+uid:u::::1538985067::8200BD0425CC70C7D698DF3FE412044EAAB83F94::testtest::::::::::0
+sig:!::1:0E41076773CB19F7:1538985067::::monkeymonkey:13x::85763FA8731311FE9C1EB3710E41076773CB19F7:::8
FAILED!
### removing temp dir...
make: *** [Makefile:117: test-keytrans] Error 1
==> ERROR: A failure occurred in check().
    Aborting...

Command 'makepkg --force' failed to execute.

I am guessing it tries to import a test in the build process, but notices something different? The keys look pretty similar, apart for some trailing stuff: ::::::::::0

Ghul commented on 2018-09-13 10:38 (UTC) (edited on 2018-09-13 10:38 (UTC) by Ghul)

Build complains about :

### reconvert key, and compare to key in gpg keyring...
./tests/keytrans: ligne 112: hd : command not found
./tests/keytrans: ligne 112: hd : command not found

Which tool am I missing ? Is it possible to build without running tests ?

mSSM commented on 2018-09-11 09:49 (UTC) (edited on 2018-09-11 09:51 (UTC) by mSSM)

I am getting a different error, this one related to the Crypt::OpenSSL::RSA not being found, which however is clearly installed through the perl-crypt-openssl-rsa dependency:

==> Starting check()...
MONKEYSPHERE_TEST_NO_EXAMINE=true ./tests/keytrans
You must have the perl module Crypt::OpenSSL::RSA installed to run this test. 
On debian-derived systems, you can set this up with:
apt-get install libcrypt-openssl-rsa-perl
make: *** [Makefile:117: test-keytrans] Error 1
==> ERROR: A failure occurred in check().
Aborting...

eomanis commented on 2017-05-07 15:45 (UTC)

I'm also getting the same build error as seppia: (...) ################################################## Monkeysphere keytrans test completed successfully! ################################################## ### removing temp dir... gpg: can't connect to the agent: File name too long gpg: error getting the KEK: No agent running gpg: Total number processed: 1 gpg: imported: 1 gpg: secret keys read: 1 gpg: no ultimately trusted keys found FAILED! ### removing temp dir... make: *** [Makefile:114: test-basic] Error 2 ==> ERROR: A failure occurred in check(). Aborting... :: failed to build monkeysphere package(s)

seppia commented on 2016-10-20 11:34 (UTC)

There's been an update and we'got a different fail in testing phase. Gpg still can't connect to the agent (which by the way in my case is always running since I'm still using an old version of monkeyshpere without any issue) and this time seems it complains that there is some "file name too long". In a clean system just installed the error is different and says "invalid value passed to IPC" and as if it ins't enough in this case the installing script can't even find the agent. Anyway this is the log from the install try on my usual system: ################################################## ### setup monkeysphere authentication... ms: checking authentication directory structure... ms: writing core gpg.conf... ms: writing sphere gpg.conf... ms: fixing sphere gnupg home ownership... ms: determining core key fingerprint... ms: core fingerprint: ms: setting up Monkeysphere authentication trust core... ms: generating monkeysphere authentication trust core key: ms: size: 1024 bits ms: uid: 'Monkeysphere authentication trust core UID (random string: jiMrFYZaiXO7ZOlvVxtxXc5E7iB7)' gpg: can't connect to the agent: File name too long gpg: error getting the KEK: No agent running Could not import new key for Monkeysphere authentication trust core FAILED! ### removing temp dir... make: *** [Makefile:115: test-basic] Error 255 @svalo wrote: As yaourt -just to make and example- creates several subfolders where to build the package into this can be the case, can you try to build it with a plain makepkg in the folder where you downloaded the PKGBUILD being sure the path isn't too long? that doesn't change anything since I always got these errors not using yaourt and i've tryed in every possible folder of every possible user with every possible permission and all of their combination.

starfry commented on 2016-10-12 11:06 (UTC)

You could just comment out the "make test" in the PKGBUILD... I was only after "openpgp2ssh" and that worked for me :)

svalo commented on 2016-10-05 20:33 (UTC) (edited on 2016-10-05 20:41 (UTC) by svalo)

@Sc4ryb3ar, @beardedlinuxgeek, @seppia: Regarding the "can't connect to agent" I reported the error to the devs, they suggest to control whether the lenght of the path the socket is created into exceeds 108 characters, see https://linux.die.net/man/7/unix , section "Address format" EDIT: As yaourt -just to make and example- creates several subfolders where to build the package into this can be the case, can you try to build it with a plain makepkg in the folder where you downloaded the PKGBUILD being sure the path isn't too long? @Sc4ryb3ar: the reason of the warning is that to execute some of the tests the folder -and its parents- has to be owned and writable only by the user which is running the test. It is not the case of /tmp. This is because of the requirements of sshd'strict mode. The warning will lead to some tests to being executed but should not lead to a failure.

Sc4ryb3ar commented on 2016-10-02 21:28 (UTC)

I have tried everything under the sun to get past the "can't connect to the agent" "error getting KEK", and I can't find a way to do it, to get this installed. Anyone have any solutions?

Sc4ryb3ar commented on 2016-10-01 00:17 (UTC)

So I used this, and it got past the test.... yaourt -S --tmp /home/<username> monkeysphere and it errrored out with this Monkeysphere keytrans test completed successfully! ################################################## ### removing temp dir... gpg: can't connect to the agent: File name too long gpg: error getting the KEK: No agent running gpg: Total number processed: 1 gpg: imported: 1 gpg: secret keys read: 1 gpg: no ultimately trusted keys found FAILED! ### removing temp dir... make: *** [Makefile:115: test-basic] Error 2 ==> ERROR: A failure occurred in check(). Aborting... ==> ERROR: Makepkg was unable to build monkeysphere. ==> Restart building monkeysphere ? [y/N]

Sc4ryb3ar commented on 2016-10-01 00:00 (UTC)

I got the same message as @seppia and @beardedlinuxgeek. above the fail, there are these warnings ==> Starting check()... MONKEYSPHERE_TEST_NO_EXAMINE=true ./tests/keytrans MONKEYSPHERE_TEST_NO_EXAMINE=true ./tests/basic ################################################## ### generating openpgp key... gpg: keybox '/tmp/yaourt-tmp-scarybear/aur-monkeysphere/src/monkeysphere-0.39/tests/tmp/ms.1Su/pubring.kbx' created improper group writability on '/tmp' !!!WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING!!! Permissions on testing directory '/tmp/yaourt-tmp-scarybear/aur-monkeysphere/src/monkeysphere-0.39/tests/tmp/ms.2Gu' are too loose to do proper strict permissions checking. Some tests will be disabled or ignored. To avoid this warning (and to make sure that all tests are run properly), please run these tests within a directory that meets sshd's standards for "StrictModes yes" -- the directory (and every one of its parents) should be owned only be the user running this test or root, and should not be writable by group or other. !!!WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING!!! ################################################## ### configuring testuser home... what is the proper /tmp writability?

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