• KairuByte@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      arrow-down
      8
      ·
      edit-2
      1 year ago

      … Then you would disable auto adoption of newly connected drives into bitlocker, would you not?

      This is like complaining that the login screen pops up every time for a machine that doesn’t need security. Just change the setting instead of complaining about a niche use case.

      The majority of users won’t notice a slowdown of even 50% on an SSD. It won’t effect game performance, your network will bottleneck before your SSD in any internet download, most users don’t interact with extremely large sets of data which is needed asap on the regular.

      You’re essentially only going to have a problem, in daily use for the average user, in (un)packing large sets of data, or moving large sets of data between drives. Things most people don’t do regularly.

      So a slight alteration to my question, how exactly does this negatively affect most users in daily usage.

      • blkpws@lemmy.ml
        link
        fedilink
        arrow-up
        6
        arrow-down
        1
        ·
        1 year ago

        Okay xD go ahead… but encrypting the encrypted makes no sense.

        • flying_monkies@kbin.social
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          SSDs, unless you buy a specifically encryption supported drive, are not encrypted. If it doesn’t indicate SED, SED non-FIPS or a FIPS certification level, the drive doesn’t have an encryption circuit.

          • blkpws@lemmy.ml
            link
            fedilink
            arrow-up
            3
            arrow-down
            2
            ·
            1 year ago

            I said nothing about adding more encryption, in fact I said the opposite.

            But is what Microsoft is doing here. Most SSD already has hardware level encryption… is what I said on the first comment…