Package Details: cryptmount 6.3.0-1

Git Clone URL: https://aur.archlinux.org/cryptmount.git (read-only, click to copy)
Package Base: cryptmount
Description: Utility allowing an ordinary user to mount an encrypted file system
Upstream URL: https://github.com/rwpenney/cryptmount
Licenses: GPL
Submitter: None
Maintainer: harrietobrien
Last Packager: harrietobrien
Votes: 23
Popularity: 0.009029
First Submitted: 2007-08-20 09:59 (UTC)
Last Updated: 2024-11-17 03:32 (UTC)

Latest Comments

1 2 Next › Last »

wooperz commented on 2024-08-15 16:07 (UTC) (edited on 2024-08-15 16:08 (UTC) by wooperz)

v6.3.0 appears to fix the issues mentioned recently. Here's a diff for the PKGBUILD:


5,6c5,6
< pkgver=6.2.0
< _pkgver=6.2
---
> pkgver=6.3.0
> _pkgver=6.3
10c10
< url="http://cryptmount.sourceforge.net/"
---
> url="https://github.com/rwpenney/cryptmount"
13c13
< source=(http://downloads.sourceforge.net/project/cryptmount/cryptmount/cryptmount-$_pkgver/cryptmount-$pkgver.tar.gz)
---
> source=(https://github.com/rwpenney/cryptmount/archive/refs/tags/v$pkgver.tar.gz)
15c15
< sha512sums=('005d9333792a567515ce6d487d2dfa18f19cb077a64d9c356562acefc1947581d2d0f584ad623e0aab8aed1b34f1614af3a42f0c582d31e0831cdb8eb22bb7ce')
---
> sha512sums=('15f19a1ff7409b35be2cde3d791c8d476c98ffcaf3dd9217076703b0e0baafe999a0608a88cc51039ba2e9c26cb297261128a5efeacd1a6397c5d3300886ac4d')
18a19,23
>   libtoolize --force
>   aclocal
>   autoheader
>   automake --force-missing --add-missing
>   autoconf

jrvarma commented on 2024-07-16 10:19 (UTC) (edited on 2024-07-16 10:22 (UTC) by jrvarma)

I do not know whether this is the right place to report this problem, but any suggestions would be helpful.

After upgrading Arch Linux earlier this month, cryptmount stopped working. More precisely, cryptmount decrypts the Luks encrypted partition and creates the device mapper /dev/mapper/xxx correctly, but it does not mount this at the cmtab mount point. Therefore when cryptmount runs e2fsck, the latter reports the error:

Error determining size of the physical device: No such file or directory

If I do sudo mount /dev/mapper/xxx /mnt/mountpoint after cryptmount has exited with the above error, then the mount succeeds and everything is fine.

I downgraded the three dependencies of cryptmount (libgcrypt, device-mapper, util-linux) and also reinstalled cryptmount, but these did not solve the problem.

Feakster commented on 2020-12-09 14:59 (UTC) (edited on 2020-12-15 10:35 (UTC) by Feakster)

Hi, a member of the Manjaro community has come up with a patch for the config.guess file present in the source tar.gz archive. The patch enables the detection of aarch64 hardware:

diff -ruP a/config.guess b/config.guess
--- a/config.guess  2020-11-07 08:33:43.350091075 -0600
+++ b/config.guess  2020-11-07 08:31:51.377540483 -0600
@@ -156,6 +156,7 @@
    case "${UNAME_MACHINE_ARCH}" in
        armeb) machine=armeb-unknown ;;
        arm*) machine=arm-unknown ;;
+       aarch64) machine=arm-unknown ;;
        sh3el) machine=shl-unknown ;;
        sh3eb) machine=sh-unknown ;;
        *) machine=${UNAME_MACHINE_ARCH}-unknown ;;
@@ -163,7 +164,7 @@
    # The Operating System including object format, if it has switched
    # to ELF recently, or will in the future.
    case "${UNAME_MACHINE_ARCH}" in
-       arm*|i386|m68k|ns32k|sh3*|sparc|vax)
+       arm*|aarch64|i386|m68k|ns32k|sh3*|sparc|vax)
        eval $set_cc_for_build
        if echo __ELF__ | $CC_FOR_BUILD -E - 2>/dev/null \
            | grep __ELF__ >/dev/null
@@ -827,6 +828,9 @@
     arm*:Linux:*:*)
    echo ${UNAME_MACHINE}-unknown-linux-gnu
    exit 0 ;;

Currently, config.guess cannot detect detect aarch64 hardware, and the installation fails.

Until now, I've been working around this with a crude PKGBUILD, but it would be nice to be able to retire it.

mksplg commented on 2017-12-18 20:05 (UTC)

Package is currently broken for me.

Changing the source to http://downloads.sourceforge.net/project/cryptmount/cryptmount/cryptmount-5.2/cryptmount-5.2.3.tar.gz and updating the md5sums fixes this.

Thah commented on 2017-07-29 07:41 (UTC)

In addition to v5.2.2 being released, util-linux 2.30 removed the "Provides: util-linux-ng" tag and cryptmount's runtime dependency needs to be updated. Furthermore, I suggest exchanging the role of $pkgver and $_pkgver in the PKGBUILD.

mikesd commented on 2015-01-03 14:06 (UTC)

Made Jonathan's proposed change.

Jonathan commented on 2014-12-30 20:06 (UTC)

Cryptmount's configure script defaults installation to /usr/sbin which appears to be a no longer valid install path in Arch ( https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ ). I recommend adding the --sbindir= flag when running the configure script to force installation into /usr/bin. For example: build() { cd "$srcdir/$pkgname-$pkgver" ./configure --prefix=/usr --sysconfdir=/etc --sbindir=/usr/bin make }

neocturne commented on 2013-06-05 20:28 (UTC)

Please mark /etc/cryptmount/cmtab as a backup file, it's really annoying that it's lost after every update...

polslinux commented on 2012-01-22 21:02 (UTC)

# Maintainer: Mike Sampson <mike at sambodata dot com> # Contributor: Paolo Stivanin <admin@polslinux.it> pkgname=cryptmount pkgver=4.2.1 pkgrel=1 pkgdesc="utility which allows an ordinary user to mount an encrypted file system" arch=('i686' 'x86_64') url="http://cryptmount.sourceforge.net/" license=('GPL') depends=(libgcrypt device-mapper util-linux-ng) source=(http://downloads.sourceforge.net/project/cryptmount/cryptmount/cryptmount-4.2/cryptmount-4.2.1.tar.gz) md5sums=('8ee4908d55c5b71f9becae7678d49e17') build() { cd "$srcdir/$pkgname-$pkgver" install -d "$pkgdir/usr/sbin"; ./configure --prefix=/usr --sysconfdir=/etc make || return 1 make DESTDIR="$pkgdir" install }

mikesd commented on 2010-08-09 02:20 (UTC)

Updated to v4.1. There are still a couple of NAMCAP warnings to fix when I get a chance.

1 2 Next › Last »