dm-crypt.saout.de archive mirror
 help / color / mirror / Atom feed
From: "Wei, Catherine" <catherine.wei@commscope.com>
To: Milan Broz <gmazyland@gmail.com>,
	"dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: [dm-crypt] Re: veritysetup and CentOS 8
Date: Tue, 26 Oct 2021 08:07:55 +0000	[thread overview]
Message-ID: <PH0PR14MB4535E6EE623DD81AED1620DBED849@PH0PR14MB4535.namprd14.prod.outlook.com> (raw)
In-Reply-To: <PH0PR14MB4535EFBF30DF57ECB89E5E06EDBC9@PH0PR14MB4535.namprd14.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 3026 bytes --]

Hi if you have answers to the questions in following email, please let me know. Really appreciate if you’d help.

Best regards,
Catherine

From: Wei, Catherine
Sent: 2021年10月18日 15:02
To: Milan Broz <gmazyland@gmail.com>
Subject: RE: [dm-crypt] veritysetup and CentOS 8

Hi Broz.
The reason we don’t want to use cryptsetup 2.0 is that it required new libs such as “json-c” and now many of our build servers haven’t install this library, and it also need us to make some modifications on gcc in the build servers.
We have only one centos 8 build server, and many centos 7 build servers. In CentOS 7 build server, the veritysetup (1.7.5) could run, but not on the one CentOS 8.

So we prefer to modify the only CentOS 8 to make the veritysetup command works instead of update all the CentOS 7 servers.


Regarding the
> Also CentOS kernel has own options, not everything is available there (e.g. FEC support for dm-verity is not compiled in IIRC).

We run commands like this:
“veritysetup format --no-superblock $our_rootdisk $verity_hashdevice”

The veritysetup command was built from cryptsetup 1.7.5. Does this command require special support from kernel such as FEC support for dm-verity?


Best regards,
Catherine

From: Milan Broz <gmazyland@gmail.com<mailto:gmazyland@gmail.com>>
Sent: 2021年10月15日 16:27
To: Wei, Catherine <catherine.wei@commscope.com<mailto:catherine.wei@commscope.com>>
Subject: Re: [dm-crypt] veritysetup and CentOS 8

On 14/10/2021 10:23, Wei, Catherine wrote: > Hi all, > > I found that the veritysetup built from cryptsetup-1.7.5 couldn’t work in CentOS 8.2, when I run veritysetup command on the CentOS 8, it report
Caution: External (gmazyland@gmail.com<mailto:gmazyland@gmail.com>)
First-Time Sender   Details<https://shared.outlook.inky.com/details?id=Y29tbXNjb3BlL2NhdGhlcmluZS53ZWlAY29tbXNjb3BlLmNvbS80NTI1ZjE0ZjhjNjUxNDkxOGExYzFmODY3MzA1ZDdlOS8xNjM0Mjg2NDQ3Ljc1#key=27420ad8a6087eb0deb487e7bba8aa5c>
  Report This Email<https://shared.outlook.inky.com/report?id=Y29tbXNjb3BlL2NhdGhlcmluZS53ZWlAY29tbXNjb3BlLmNvbS80NTI1ZjE0ZjhjNjUxNDkxOGExYzFmODY3MzA1ZDdlOS8xNjM0Mjg2NDQ3Ljc1#key=27420ad8a6087eb0deb487e7bba8aa5c>  FAQ<https://www.inky.com/banner-faq/>  Protection by INKY<https://www.inky.com>


On 14/10/2021 10:23, Wei, Catherine wrote:

> Hi all,

>

> I found that the veritysetup built from cryptsetup-1.7.5 couldn’t work in CentOS 8.2, when I run veritysetup command on the CentOS 8, it reported error:

>

>

>

> veritysetup: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by veritysetup)



This cannot happen, if you compile it properly.



Just use provided version from CentOS repo.



Also CentOS kernel has own options, not everything is available there (e.g. FEC support for dm-verity is not compiled in IIRC).



Anyway, this is upstream list, version 1.7.5 is 4 years old, why are you using that?

(CentOS8 stream repo provides 2.3.3, at least).



Milan

[-- Attachment #1.2: Type: text/html, Size: 10305 bytes --]

[-- Attachment #2: Type: text/plain, Size: 147 bytes --]

_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de

  parent reply	other threads:[~2021-10-29 23:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  8:23 [dm-crypt] veritysetup and CentOS 8 Wei, Catherine
2021-10-15  8:32 ` [dm-crypt] " Milan Broz
     [not found] ` <68390b56-e5b7-7f3c-74a7-6edad253df08@gmail.com>
     [not found]   ` <PH0PR14MB4535EFBF30DF57ECB89E5E06EDBC9@PH0PR14MB4535.namprd14.prod.outlook.com>
2021-10-26  8:07     ` Wei, Catherine [this message]
2021-10-26  8:13       ` Wei, Catherine
2021-10-30 10:19         ` Milan Broz
2021-11-10  6:28           ` Wei, Catherine
2021-11-10  9:42             ` Milan Broz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PH0PR14MB4535E6EE623DD81AED1620DBED849@PH0PR14MB4535.namprd14.prod.outlook.com \
    --to=catherine.wei@commscope.com \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).