On 3/5/19 11:49 PM, Jeremy Bicha wrote:
> On Tue, Mar 5, 2019 at 12:35 PM procmem wrote:
>> I stand corrected its in your version since you cherry picked the patch.
> Yes. Could you verify whether that version fixes your issue?
>
> Thanks,
> Jeremy Bicha
It does indeed. Thanks.
I stand corrected its in your version since you cherry picked the patch.
On 3/5/19 6:16 AM, Jeremy Bicha wrote:
> I just uploaded libblockdev 2.20-7. Please check if it fixes your issue.
>
> If it does, would you be interested in filing the unblock bug to get
> the fix in to Debian Buster?
>
> https://release.debian.org/buster/freeze_policy.html
>
> Thanks,
> Jeremy B
Jeremy Bicha:
> On Wed, Oct 3, 2018 at 6:36 PM procmem wrote:
>> Package: gnome-disk-utility
>> Version: all
>> Severity: serious
>>
>> Hi. I noticed Gnome Disks uses AES-128 by default instead of AES-256
>> like Debian does out of the box. Having 256 bit
Package: gnome-disk-utility
Version: all
Severity: serious
Hi. I noticed Gnome Disks uses AES-128 by default instead of AES-256
like Debian does out of the box. Having 256 bit symmetric keys is good
practice for long term security especially in a coming era of quantum
computers. (Whether they mate
Please disregard what I said in the background section of my original
post. I will correct a few factual errors.
Qunatum computing has nothing to do with using Argon2id.
Argon2id promises up to a quadratic increase in mitgating GPUs vs the
linear protection of PBKDF2-HMAC-SHA*. PBKDF2-HMAC-SHA* i
Good to see you guys here. Debian packaging is in good hands. Thanks for
explaining the roadmap and for the support on the dm-crypt ML.
@Milan Broz
Apologies. I am not an expert by any means and did not know all the
implications of the command posted. So are you saying that using forced
iterations
Package: cryptsetup
Version: 2:2.0.4-2
Severity: important
Dear Maintainer,
As part of my work on a downstream privacy distro I asked the cryptsetup
team on how to transition current LUKS1 systems to use the improved
argon2id algo for the PBKDF implementation when using LUKS2.
Background:
While
W. Martin Borgert:
> On 2018-06-23 17:21, procmem wrote:
>> Package: gajim
>> Version: all
>> Severity: serious
>>
>> Please consider packaging the plugin installer separately (to make its
>> install optional) as it prompts users to update and install ad
Package: gajim
Version: all
Severity: serious
Please consider packaging the plugin installer separately (to make its
install optional) as it prompts users to update and install additional
code from untrusted sources which violates Debian's package security
assumptions.
(/usr/share/gajim/plugins/p
10 matches
Mail list logo
