Maybe there is a problem applying the 2.18 patch to the 2.19 ebuild. ---------------- * Messages for package sys-apps/util-linux-2.19: * Package: sys-apps/util-linux-2.19 * Repository: gentoo * Maintainer: base-system@gentoo.org * USE: amd64 cramfs crypt elibc_glibc kernel_linux loop-aes multilib nls perl test unicode userland_GNU * FEATURES: ccache nostrip sandbox test userpriv usersandbox * Applying util-linux-ng-2.18-20100706.diff ... * Failed Patch: util-linux-ng-2.18-20100706.diff ! * ( /var/tmp/portage/sys-apps/util-linux-2.19/work/util-linux-ng-2.18-20100706.diff ) Reproducible: Always Steps to Reproduce: emerge -v1 util-linux (resp. "emerge -vuD world") $ sudo emerge -v1 --info -p util-linux Portage 2.1.9.39 (default/linux/amd64/10.0/desktop, gcc-4.4.5, glibc-2.12.2-r0, 2.6.35-gentoo-r6 x86_64) ================================================================= System Settings ================================================================= System uname: Linux-2.6.35-gentoo-r6-x86_64-Intel-R-_Core-TM-2_Duo_CPU_T6400_@_2.00GHz-with-gentoo-2.0.1 Timestamp of tree: Fri, 11 Feb 2011 09:30:01 +0000 ccache version 3.1.4 [enabled] app-shells/bash: 4.1_p9 dev-lang/python: 2.6.6-r1, 2.7.1, 3.1.3 dev-util/ccache: 3.1.4 dev-util/cmake: 2.8.3-r1 sys-apps/baselayout: 2.0.1-r1 sys-apps/openrc: 0.7.0 sys-apps/sandbox: 2.4 sys-devel/autoconf: 2.13, 2.68 sys-devel/automake: 1.9.6-r3, 1.10.3, 1.11.1 sys-devel/binutils: 2.21 sys-devel/gcc: 4.4.5, 4.5.2 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.4-r1 sys-devel/make: 3.82 virtual/os-headers: 2.6.36.1 (sys-kernel/linux-headers) ABI="amd64" ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="* -@EULA" ACCEPT_PROPERTIES="*" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ARCH="amd64" ASFLAGS_x86="--32" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CCACHE_DIR="/var/tmp/ccache" CCACHE_SIZE="2G" CDEFINE_amd64="__x86_64__" CDEFINE_x86="__i386__" CFLAGS="-O1 -pipe -march=core2 -ggdb" CFLAGS_x86="-m32" CHOST="x86_64-pc-linux-gnu" CHOST_amd64="x86_64-pc-linux-gnu" CHOST_x86="i686-pc-linux-gnu" CLEAN_DELAY="5" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" COLLISION_IGNORE="/lib/modules" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CVS_RSH="ssh" CXXFLAGS="-O1 -pipe -march=core2 -ggdb" DEFAULT_ABI="amd64" DISPLAY=":0" DISTDIR="/var/portage/distfiles" ELIBC="glibc" EMERGE_DEFAULT_OPTS="-v" EMERGE_LOG_DIR="/var/log/portage" EMERGE_WARNING_DELAY="10" EPREFIX="" EROOT="/" FCFLAGS="" FEATURES="assume-digests binpkg-logs ccache distlocks fixlafiles fixpackages news nostrip parallel-fetch protect-owned sandbox sfperms strict stricter test unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox" FETCHCOMMAND="/usr/bin/wget -t 3 -T 60 --passive-ftp -O "${DISTDIR}/${FILE}" "${URI}"" FETCHCOMMAND_RSYNC="rsync -avP "${URI}" "${DISTDIR}/${FILE}"" FETCHCOMMAND_SFTP="bash -c "x=\${2#sftp://} ; host=\${x%%/*} ; port=\${host##*:} ; host=\${host%:*} ; [[ \${host} = \${port} ]] && port=22 ; exec sftp -P \${port} \"\${host}:/\${x#*/}\" \"\$1\"" sftp "${DISTDIR}/${FILE}" "${URI}"" FETCHCOMMAND_SSH="bash -c "x=\${2#ssh://} ; host=\${x%%/*} ; port=\${host##*:} ; host=\${host%:*} ; [[ \${host} = \${port} ]] && port=22 ; exec rsync --rsh=\"ssh -p\${port}\" -avP \"\${host}:/\${x#*/}\" \"\$1\"" rsync "${DISTDIR}/${FILE}" "${URI}"" FFLAGS="" FLTK_DOCDIR="/usr/share/doc/fltk-1.3.0_rc3-r1/html" GCC_SPECS="" GDK_USE_XFT="1" GENTOO_MIRRORS="http://distfiles.gentoo.org" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" GSETTINGS_BACKEND="gconf" GUILE_LOAD_PATH="/usr/share/guile/1.8" HOME="/root" INFOPATH="/usr/share/info:/usr/share/binutils-data/x86_64-pc-linux-gnu/2.21/info:/usr/share/gcc-data/x86_64-pc-linux-gnu/4.4.5/info:/usr/share/info/emacs-23" INPUT_DEVICES="evdev synaptics" KERNEL="linux" LANG="de_DE.UTF-8" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LC_COLLATE="C" LDFLAGS="-Wl,-O1 -Wl,--as-needed" LDFLAGS_x86="-m elf_i386" LESS="-R -M --shift 5" LESSOPEN="|lesspipe.sh %s" LIBDIR_amd64="lib64" LIBDIR_amd64_fbsd="lib64" LIBDIR_ppc="lib32" LIBDIR_ppc64="lib64" LIBDIR_sparc32="lib32" LIBDIR_sparc64="lib64" LIBDIR_x86="lib32" LIBDIR_x86_fbsd="lib32" LINGUAS="de" LOGNAME="root" LS_COLORS="rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.pdf=00;32:*.ps=00;32:*.txt=00;32:*.patch=00;32:*.diff=00;32:*.log=00;32:*.tex=00;32:*.doc=00;32:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:" MAIL="/var/mail/root" MAKEOPTS="-j3" MANPATH="/usr/local/share/man:/usr/share/man:/usr/share/binutils-data/x86_64-pc-linux-gnu/2.21/man:/usr/share/gcc-data/x86_64-pc-linux-gnu/4.4.5/man" MULTILIB_ABIS="amd64 x86" MULTILIB_STRICT_DENY="64-bit.*shared object" MULTILIB_STRICT_DIRS="/lib32 /lib /usr/lib32 /usr/lib /usr/kde/*/lib32 /usr/kde/*/lib /usr/qt/*/lib32 /usr/qt/*/lib /usr/X11R6/lib32 /usr/X11R6/lib" MULTILIB_STRICT_EXEMPT="(perl5|gcc|gcc-lib|binutils|eclipse-3|debug|portage)" NETBEANS="apisupport cnd groovy gsf harness ide identity j2ee java mobility nb php profiler soa visualweb webcommon websvccommon xml" OPENGL_PROFILE="xorg-x11" PATH="/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin" PHP_TARGETS="php5-3" PKGDIR="/var/portage/packages" PORTAGE_ARCHLIST="ppc sparc64-freebsd ppc-openbsd x86-openbsd ppc64 x86-winnt x86-fbsd ppc-aix alpha arm x86-freebsd s390 amd64 arm-linux x86-macos x64-openbsd ia64-hpux hppa x86-netbsd x86-cygwin amd64-linux ia64-linux x86 sparc-solaris x64-freebsd sparc64-solaris x86-linux x64-macos sparc m68k-mint ia64 mips ppc-macos x86-interix hppa-hpux amd64-fbsd x64-solaris mips-irix m68k sh x86-solaris sparc-fbsd" PORTAGE_BINHOST_CHUNKSIZE="3000" PORTAGE_BIN_PATH="/usr/lib64/portage/bin" PORTAGE_COMPRESS_EXCLUDE_SUFFIXES="css gif htm[l]? jp[e]?g js pdf png" PORTAGE_CONFIGROOT="/" PORTAGE_DEBUG="0" PORTAGE_DEPCACHEDIR="/var/cache/edb/dep" PORTAGE_ELOG_CLASSES="info warn error log qa" PORTAGE_ELOG_MAILFROM="portage@localhost" PORTAGE_ELOG_MAILSUBJECT="[portage] ebuild log for ${PACKAGE} on ${HOST}" PORTAGE_ELOG_MAILURI="root" PORTAGE_ELOG_SYSTEM="save_summary echo" PORTAGE_FETCH_CHECKSUM_TRY_MIRRORS="5" PORTAGE_FETCH_RESUME_MIN_SIZE="350K" PORTAGE_GID="250" PORTAGE_INST_GID="0" PORTAGE_INST_UID="0" PORTAGE_PYM_PATH="/usr/lib64/portage/pym" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_RSYNC_RETRIES="-1" PORTAGE_SANDBOX_COMPAT_LEVEL="16" PORTAGE_SYNC_STALE="30" PORTAGE_TMPDIR="/var/tmp" PORTAGE_VERBOSE="1" PORTAGE_WORKDIR_MODE="0700" PORTDIR="/var/portage" PORTDIR_OVERLAY="/var/portage/local" PORT_LOGDIR="/var/log/portage" PRELINK_PATH_MASK="/usr/lib64/klibc:/usr/lib64/libfreebl3.so:/usr/lib64/libnssdbm3.so:/usr/lib64/libsoftokn3.so" PROFILE_ONLY_VARIABLES="ARCH ELIBC KERNEL USERLAND" PYTHONDONTWRITEBYTECODE="1" QEMU_SOFTMMU_TARGETS="i386 x86_64" QEMU_USER_TARGETS="i386 x86_64" RESUMECOMMAND="/usr/bin/wget -c -t 3 -T 60 --passive-ftp -O "${DISTDIR}/${FILE}" "${URI}"" RESUMECOMMAND_RSYNC="rsync -avP "${URI}" "${DISTDIR}/${FILE}"" RESUMECOMMAND_SSH="bash -c "x=\${2#ssh://} ; host=\${x%%/*} ; port=\${host##*:} ; host=\${host%:*} ; [[ \${host} = \${port} ]] && port=22 ; exec rsync --rsh=\"ssh -p\${port}\" -avP \"\${host}:/\${x#*/}\" \"\$1\"" rsync "${DISTDIR}/${FILE}" "${URI}"" ROOT="/" ROOTPATH="/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.4.5" RPMDIR="/var/portage/rpm" RUBY_TARGETS="ruby18" SANE_BACKENDS="artec_eplus48u" SANE_CONFIG_DIR="/etc/sane.d" SCHEME_LIBRARY_PATH="/usr/share/slib/" SHELL="/bin/bash" STAGE1_USE="multilib nptl nptlonly unicode" SUDO_COMMAND="/usr/bin/emerge -v1 --info -p util-linux" SUDO_GID="100" SUDO_UID="1000" SUDO_USER="atti" SYMLINK_LIB="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" TERM="xterm" TMPDIR="/var/tmp" USB_DEVFS_PATH="/dev/bus/usb" USE="X a52 aac acl acpi alsa amd64 bash-completion berkdb boundschecking branding bzip2 cairo ccache cdinstall cdr clamav cli consolekit cracklib crypt cups cupsddk cxx dbus dga directfb dri dts dvd dvdnav dvdr emboss encode exif fam fbcon firefox flac fortran gdbm gdu gif gkrellm glitz gmp gnutls gpm gtk hal hddtemp hpn iconv icu idn ipv6 ithreads jpeg jpeg2k laptop lcms libnotify libsamplerate lm_sensors loop-aes lzma mad md5sum mem-scramble memlimit mikmod mmap mmx mng modules mp3 mp4 mpeg mtrr mudflap multilib ncurses nls nptl nptlonly nvidia offensive ogg opengl openmp openvg pam pango pcre pda pdf perl pmu png policykit ppds pppd pth pulseaudio python readline rtc sdl session smp spell sse sse2 sse3 ssl ssse3 startup-notification svg sysfs tcpd threads threadsafe tiff tordns truetype udev unicode usb vaapi videos vorbis x264 xcb xml xorg xulrunner xv xvid xvmc zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="evdev synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de" PHP_TARGETS="php5-3" QEMU_SOFTMMU_TARGETS="i386 x86_64" QEMU_USER_TARGETS="i386 x86_64" RUBY_TARGETS="ruby18" SANE_BACKENDS="artec_eplus48u" USERLAND="GNU" VIDEO_CARDS="nouveau" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" USER="root" USERLAND="GNU" USERNAME="root" USE_EXPAND="ALSA_CARDS ALSA_PCM_PLUGINS APACHE2_MODULES APACHE2_MPMS CAMERAS COLLECTD_PLUGINS CROSSCOMPILE_OPTS DVB_CARDS ELIBC FCDSL_CARDS FOO2ZJS_DEVICES FRITZCAPI_CARDS GPSD_PROTOCOLS INPUT_DEVICES KERNEL LCD_DEVICES LINGUAS LIRC_DEVICES MISDN_CARDS NETBEANS_MODULES NGINX_MODULES_HTTP NGINX_MODULES_MAIL PHP_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS RUBY_TARGETS SANE_BACKENDS USERLAND VIDEO_CARDS XFCE_PLUGINS XTABLES_ADDONS" USE_EXPAND_HIDDEN="CROSSCOMPILE_OPTS ELIBC KERNEL USERLAND" USE_ORDER="env:pkg:conf:defaults:pkginternal:env.d" VIDEO_CARDS="nouveau" XAUTHORITY="/home/atti/.Xauthority" XDG_CONFIG_DIRS="/etc/xdg" XDG_DATA_DIRS="/usr/local/share:/usr/share" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" XZ_OPT="--memory=max" ================================================================= Package Settings ================================================================= sys-apps/util-linux-2.18-r1 was built with the following: USE="crypt loop-aes (multilib) nls perl test unicode -old-linux (-selinux) -slang (-uclibc)" CFLAGS="-O2 -pipe -march=core2" CXXFLAGS="-O2 -pipe -march=core2"
Created attachment 262099 [details] patch output
Yes, the patch hasn't been updated yet.
*** Bug 354477 has been marked as a duplicate of this bug. ***
*** Bug 354641 has been marked as a duplicate of this bug. ***
*** Bug 354677 has been marked as a duplicate of this bug. ***
I'm curious why this package was updated in the portage tree _before_ the patch(es) we're updated? Shoulda been obvious this would then fail for anyone with +loop-aes. Talk about bad practice.
ah, so adorable you think that's OK. there's no way in hell we're going to let such a vastly important package depend on some random patch with a spotty record. clearly you havent searched for the history behind this patch before posting your comment. if you want to do some *actual* work, look into getting the loop-aes sources merged into the respective mainline projects.
Yep well none of the maintainers/devs have bothered to add those reasons here, nor make a news item for it, or... anything to help smooth the process.
(In reply to comment #8) > Yep well none of the maintainers/devs have bothered to add those reasons here, > nor make a news item for it, or... anything to help smooth the process. > Well loop-aes required cryptoloop kernel support and that has been replaced by dm crypt support. For reasons why cryptoloop was replaced I suggest you ask google. It's been years since I used loop-aes and after dm crypt was introduced I never looked back.
we are not your search monkeys
*** Bug 358111 has been marked as a duplicate of this bug. ***
Well, maintainers, perhaps the reporters wanted to prod you into masking the "loop-aes" USE flag, in order for the package to be in compliance with the Gentoo policy on USE flags: "No combination of USE flags should cause a package to fail to build because users can set any combination of flags," according to the manual: http://devmanual.gentoo.org/general-concepts/use-flags/ .
i'm tired of this crap. USE=loop-aes no longer exists and will not be available in future versions of util-linux.
Would you please keep USE=loop-aes in the ebuild, at least keyworded, even if the patch takes a while. Better late than never. I really need the support for loop-aes, and I think I'am not the only one.
(In reply to comment #14) > Would you please keep USE=loop-aes in the ebuild, at least keyworded, even if > the patch takes a while. Better late than never. > I really need the support for loop-aes, and I think I'am not the only one. instead of living in 2004, why don't you just migrate to dmcrypt or manage the patch yourself in an overlay. This bug should stay close, let developers focus on real issues not crap from 2004.
no. i'm tired of dealing with crap from people over this stupid patch.
People still needing util-linux with loop-aes can find ebuilds in the poly-c overlay. Please keep in mind that I don't do much testing with these patches and that I can only add patches to newer versions when the loop-aes developer releases new patches.
This is a pretty painful change. Would it be possible to, say, break if USE=loop-aes is set? (Mark the flag deprecated? I don't know.) Users of loop-aes should be used by now to masking a brand-new util-linux ebuild until the patch has been updated by the loop-aes author. A week or two later (or by the time -r1 comes out for other reasons) it'll be good go to. I've always been perfectly OK with this arrangement (if the ebuild masked itself if the loop-aes patch wasn't yet up to date that would've been even better, but no big deal). But with this change (similar to the change from USE=crypt to USE=loop-aes some time ago), a loop-aes user who's not paying close attention can have their util-linux tools suddenly, silently forget about loop-aes support after a fairly routine update world. This could lead to a non-working system. If a system requires loop-aes support in util-linux in order to function, it would be much better for the upgrade to fail until the user has made other arrangements.
*** Bug 365889 has been marked as a duplicate of this bug. ***
*** Bug 366479 has been marked as a duplicate of this bug. ***
loop-aes is the strongest (cryptograph wise) solution. 2004 or not, this is the choice if you like strong cryptography. Just broke my system, as I upgraded to newer util-linux and had no USE conflict. loop-aes depends on crypt USE which is totally wrong. There is no sense in leaving loop-aes in tree if util-linux in tree does not support it. And I don't understand why you claim that you get a lot of heat... the only problem is the delay that there is between util-linux release and when the patch is available. So please, either remove loop-aes from tree or support it properly.
Another thing about loop-aes vs dm-crypt: dm-crypt is really slow. At my system on a ssd (255mb/s read) it is 130mb/s (dm-crypt) vs 195mb/s (loop-aes) with the same encryption settings. That's a big deal I think. So it would be really cool to keep on supporting loop-aes.
(In reply to comment #7) > if you want to do some *actual* work, look into getting the loop-aes sources > merged into the respective mainline projects. You probably know as well as anyone who's been following/using loop-aes for a long time that your suggestion is about as plausible as your own willingness to keep the loop-aes keyword and handling the patches. The words 'oversized' and 'ego' come to mind. And, surely, we are all thankful for the numerous merits that tend to result in those inflated self-images... The sad fact is that -as others have argued already- loop-aes is superior on both security and performance. I'll certainly cast my vote on fixing this issue and encourage others to do the same (and keep using the poly-c ebuild in the meantime).
I do not really understand what's going on, yet. Since years I use a script with "losetup -H rmd160 -e AES256 ...." to mount local volumes and backup volumes (probably since 2002 or something). About 10mins ago I needed a file from a backup and suddenly the mount script failed. Now I found out it's because of an update of util-linux I made yesterday. So if I had done a reboot, nothing would work anymore... without a notice.. Of course I understand that things change - but at least a BIG FAT warning on emerge would have been in order, I guess. I mean this renders whole systems unusable! So, as the 'new' losetup does not work anymore like it used to, what is the proper way to mount volumes encrypted like that? (I googled, looked at the cryptsetup wiki, but am a little clueless right now) ..and I really need my backup.. Any help&pointers really appreciated!
For a temp. fix you can add ">sys-apps/util-linux-2.18-r1" to your "/etc/portage/package.mask". But you can't use that version forever. For the future there are some more options: 1) Use the ebuild from portage and add the patch by your own in a local overlay 2) Use an overlay which has a patched version in it (e.g. the poly-c overlay from layman) 3) We will be able to get the loop-aes useflag back to portage. That would be the best solution for us :/
(In reply to comment #25) > For a temp. fix you can add ">sys-apps/util-linux-2.18-r1" to your > "/etc/portage/package.mask". But you can't use that version forever. > > For the future there are some more options: > > 1) Use the ebuild from portage and add the patch by your own in a local overlay > 2) Use an overlay which has a patched version in it (e.g. the poly-c overlay > from layman) > 3) We will be able to get the loop-aes useflag back to portage. That would be > the best solution for us :/ Actually, the best solution is: 4) Get the patches accepted upstream.
(In reply to comment #26) > Actually, the best solution is: > > 4) Get the patches accepted upstream. Long history of this. If you review the history you understand why loop-aes is outside the kernel, and why if loop-aes is external module, no patches will be merged into util-linux. But undoubtedly, loop-aes is superior encryption. Until now, Gentoo was friendly for loop-aes (security wise users). I maintained this in Gentoo for a while. The *REAL* problem here is that Gentoo maintainers broke users' systems. The DEPEND of loop-aes is totally invalid, and did not raise the problem to users. --- DEPEND="|| ( >=sys-apps/util-linux-2.12r[crypt] >=sys-apps/util-linux-2.12r[loop-aes] )" --- Also, if util-linux does not support loop-aes, the loop-aes and aespipe should also moved out side of tree. So either fix this properly by depreciating the loop-aes from the whole tree, mask it first and then remove. Or support it properly.
mmmh.. does this mean that without this specific patch there is no other way to mount the volumes?! So support for plain AES volumes was just deleted without an alternative? And that in a minor update without any warning?!
Welcome to the wonderful world of Linux cryptography. It's not just loop-aes either, back in the 2.4 kernel series there was an incompatible change in the cyphers (2.4.21->22, IIRC) which also meant you couldn't mount your volumes any more, and in the cryptsetup package they managed to change the config-file format from 1.0.3 to 1.0.4 in such a way that a valid 1.0.3 file with crypto-home and swap would in 1.0.4 create the crypto-swap on what was supposed to be your home partition instead. Obviously a lot of the people involved in these crypto-packages lack even the most basic understanding that they're severely screwing with people's actual DATA. If any of this happened with regular filing systems, none of them would ever submit a single line of code again. My actual partitions are running with dm-crypt, but I also have encrypted images (for backup purposes mostly), which I used with the loop. So how am I supposed to use these without it, considering dm-crypt only works on block devices? Creating a regular loop on the image so I can dm-crypt on the loop so I can mount a filing system on dm-crypt crossed the line into the ridiculous as far as I'm concerned.
As (I think) noted in this thread and on http://code.google.com/p/cryptsetup/wiki/Cryptsetup130, cryptsetup 1.3.0 (not in portage yet, but a version bump bug exists) is able to mount loop-aes images (though with performance hit).
(In reply to comment #30) > As (I think) noted in this thread and on > http://code.google.com/p/cryptsetup/wiki/Cryptsetup130, cryptsetup 1.3.0 (not > in portage yet, but a version bump bug exists) is able to mount loop-aes images > (though with performance hit). """ Please note that loopAES dm-crypt mode is provided for compatibility reasons (so you do not need to patch kernel and util-linux to map existing volumes) but is is not, and never will be, optimized for speed. It is experimental feature for now. """
take debate/support questions elsewhere
*** Bug 367641 has been marked as a duplicate of this bug. ***
Un-CCing, I am tired of these debates. Will maintain a patched version in my personal overlay.
*** Bug 370635 has been marked as a duplicate of this bug. ***
http://dev.c1pher.net/index.php/2011/06/loop-aes-should-it-be-treecleaned/
*** Bug 381521 has been marked as a duplicate of this bug. ***
