Control: tag -1 fixed-upstream
On Mon, 26 Aug 2019 at 11:08:35 +0200, Milan Broz wrote:
> Fixed here
> https://gitlab.com/cryptsetup/cryptsetup/commit/8f8f0b3258152a260c6a40be89b485f943f81484
Thanks, Milan!
> I'll do minor release soon, but perhaps it would be better to
> cherrypick the patch
On 26/08/2019 08:03, Milan Broz wrote:
> No need to report it upstream, I'll fix it. This is really stupid bug, all
> sizes in code
> must be uint_64t. I just wonder why no static analysis screamed here, I run
> it on 32bit...
Fixed here
On 26/08/2019 03:28, Guilhem Moulin wrote:
> On Sun, 25 Aug 2019 at 12:43:26 +, n...@waifu.club wrote:
>> Not only the access to protected data is lost, the integritysetup's "open"
>> operation actually succeeds. All reads on the incorrectly created DM device
>> will of course fail with I/O
Control: retitle -1 DM device size ≥2³² 512-bits sectors is truncated on
32-bits platforms
Control: tag -1 + upstream
Hi,
On Sun, 25 Aug 2019 at 12:43:26 +, n...@waifu.club wrote:
> Not only the access to protected data is lost, the integritysetup's "open"
> operation actually succeeds. All
4 matches
Mail list logo