Bug#1060422: partman-crypto: add support for new cryptsetup options for opal/sed

2024-01-15 Thread Luca Boccassi
On Mon, 15 Jan 2024 at 12:28, Holger Levsen wrote: > > On Mon, Jan 15, 2024 at 10:46:14AM +, Luca Boccassi wrote: > > > huh, if there's a bug in the firmware to accidently store the encryption > > > key on the drive in plaintext, it doesn't cost anything extra. > > Sure, and if there's a bug i

Bug#1060422: partman-crypto: add support for new cryptsetup options for opal/sed

2024-01-15 Thread Holger Levsen
On Mon, Jan 15, 2024 at 10:46:14AM +, Luca Boccassi wrote: > > huh, if there's a bug in the firmware to accidently store the encryption > > key on the drive in plaintext, it doesn't cost anything extra. > Sure, and if there's a bug in your CPU to accidentally reveal all > kernel secrets to any

Bug#1060422: partman-crypto: add support for new cryptsetup options for opal/sed

2024-01-15 Thread Luca Boccassi
On Mon, 15 Jan 2024 at 10:22, Holger Levsen wrote: > > On Sun, Jan 14, 2024 at 08:37:30PM +, Luca Boccassi wrote: > > Most definitely wrong. If your threat model is "hardware vendor will > > spend hundreds of millions of dollars to get at me" then your cpu > > vendor, memory controller vendor,

Bug#1060422: partman-crypto: add support for new cryptsetup options for opal/sed

2024-01-15 Thread Holger Levsen
On Sun, Jan 14, 2024 at 08:37:30PM +, Luca Boccassi wrote: > Most definitely wrong. If your threat model is "hardware vendor will > spend hundreds of millions of dollars to get at me" then your cpu > vendor, memory controller vendor, etc etc can do that too, so you > better not use this nor any

Bug#1060822: choose-mirror: please add support for loong64

2024-01-15 Thread John Paul Adrian Glaubitz
Hi Wuruilong, On Mon, 2024-01-15 at 02:21 +, wuruilong wrote: > Please modify Mirrors.masterlist to support loong64 architecture Please open a pull request here [1] to edit the master list. Make sure you cover all servers which already mirror loong64. Adrian > [1] https://salsa.debian.org/