linux-ext4 - Re: How to install set_encpolicy for xfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <455107637.66214831.1501836591708.JavaMail.zimbra@redhat.com>
Date:   Fri, 4 Aug 2017 04:49:51 -0400 (EDT)
From:   Carlos Eduardo Maiolino <cmaiolin@...hat.com>
To:     Dai Xiang <xiangx.dai@...el.com>
Cc:     Nikolay Borisov <n.borisov.lkml@...il.com>,
        linux-ext4@...r.kernel.org
Subject: Re: How to install set_encpolicy for xfs_io

Hi,

> > SGI have essentially abandoned all xfs-related infrastructure hosting.
> > As a result the mailing list got moved to kernel.org infrastructure and
> > the development branches as well. I'd suggest to always use the xfs
> > repos hosted on git.kernel.org
> 
> Hi, i do install as below and cp /xfsprogs to other host, i still can
> not get set_encpolicy:
> 
> 	make configure || return
> 	./configure --prefix=/xfsprogs/usr --exec_prefix=/xfsprogs/usr
> 	make || return
> 	make install
> 	make install-dev
> 
> I git clone newest codes and HEAD is:
> commit 0602fbe880e59c3aff13a081632b79532a40a328 (HEAD -> master, tag:
> v4.12.0, origin/master, origin/HEAD)
> Author: Eric Sandeen <sandeen@...deen.net>
> Date:   Thu Jul 20 10:57:14 2017 -0500
> 
>     xfsprogs: Release v4.12.0
>     
>     Update all the necessary files for a 4.12.0 release.
>     
>     Signed-off-by: Eric Sandeen <sandeen@...deen.net>
> 
> Do i miss something important?
> 
> Thanks
> Xiang
> 

No, 4.12 already has it, you are doing something else, can you run 'xfs_io -V'
and confirm you are using a xfsprogs >= 4.10?

you didn't install int in the usual prefix, so, it is likely you don't have it in your $PATH
and you are triggering an old xfsprogs version.

-- 
--Carlos