From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13251] New: cryptsetup does not work on branch 2020.02 following json-c upgrade
Date: Thu, 08 Oct 2020 08:10:42 +0000 [thread overview]
Message-ID: <bug-13251-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13251
Bug ID: 13251
Summary: cryptsetup does not work on branch 2020.02 following
json-c upgrade
Product: buildroot
Version: 2020.02.6
Hardware: All
OS: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: dominique.tronche at atos.net
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 8596
--> https://bugs.busybox.net/attachment.cgi?id=8596&action=edit
cryptsetup debug
We have integrated the last 2 tags of buildroot on branch 2020.02 which include
a patch on cryptsetup following an upgrade of json-c package, but this patch
does not seems sufficient
Our cyphered partition cannot be opened which makes our product unusable
Attached the cryptsetup command failing in debug mode
A similar issue was found on cryptsetup gitlab
https://gitlab.com/cryptsetup/cryptsetup/-/issues/556
Upgrading to cryptsetup version from master branch solved the issue
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-10-08 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 8:10 bugzilla at busybox.net [this message]
2020-10-11 21:10 ` [Buildroot] [Bug 13251] cryptsetup does not work on branch 2020.02 following json-c upgrade bugzilla at busybox.net
2020-10-12 9:04 ` bugzilla at busybox.net
2020-10-12 9:29 ` bugzilla at busybox.net
2020-10-12 9:30 ` bugzilla at busybox.net
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=bug-13251-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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