Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. I've been physically destroying several old hard drives and prepping a pile of old electronics for recycling.

I've been physically destroying several old hard drives and prepping a pile of old electronics for recycling.

Scheduled Pinned Locked Moved Uncategorized
26 Posts 8 Posters 34 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • zer0unplanned@friendica.rogueproject.orgZ zer0unplanned@friendica.rogueproject.org
    @n_dimension @kkarhan @Nonya_Bidniss there are scripts that nuke the whole OS and Kernel and DD, just 1 script to run on the pc .
    Mr Robot used the chip for a microwave and pierced a hole in the HDD, in the movie whoami they used acid indeed with a mask on.
    But just 1 script and you can overwrite the hdd or SDD or/and nuke the whole OS> I wish them good luck with that recovering anything.
    kkarhan@infosec.spaceK This user is from outside of this forum
    kkarhan@infosec.spaceK This user is from outside of this forum
    kkarhan@infosec.space
    wrote last edited by
    #16

    @zer0unplanned @Nonya_Bidniss @n_dimension there are tools like shred that do the repeat overwrites with random data, 0s & 1s.

    • Just iterate over your physical drives and you should be good
      • That does work fine, and is kinda essential with shitty hosters [i.e. Hetzner] that tend to not even replace/delete the vHDD of their VPSes after customers cancel them.
    kkarhan@infosec.spaceK zer0unplanned@friendica.rogueproject.orgZ 2 Replies Last reply
    0
    • kkarhan@infosec.spaceK kkarhan@infosec.space

      @zer0unplanned @Nonya_Bidniss @n_dimension there are tools like shred that do the repeat overwrites with random data, 0s & 1s.

      • Just iterate over your physical drives and you should be good
        • That does work fine, and is kinda essential with shitty hosters [i.e. Hetzner] that tend to not even replace/delete the vHDD of their VPSes after customers cancel them.
      kkarhan@infosec.spaceK This user is from outside of this forum
      kkarhan@infosec.spaceK This user is from outside of this forum
      kkarhan@infosec.space
      wrote last edited by
      #17

      @zer0unplanned @Nonya_Bidniss @n_dimension OFC physically destroying the drives among dozens if not hundreds of identical ones with a physical shredder is also an option, but neither cheap nor fast.

      • But in many cases that is the mandated way to do things to ease off lawyers and in any decent organization CISO & CLO will approve of it if they didn't mandate it already…
      zer0unplanned@friendica.rogueproject.orgZ 1 Reply Last reply
      0
      • kkarhan@infosec.spaceK kkarhan@infosec.space

        @zer0unplanned @Nonya_Bidniss @n_dimension there are tools like shred that do the repeat overwrites with random data, 0s & 1s.

        • Just iterate over your physical drives and you should be good
          • That does work fine, and is kinda essential with shitty hosters [i.e. Hetzner] that tend to not even replace/delete the vHDD of their VPSes after customers cancel them.
        zer0unplanned@friendica.rogueproject.orgZ This user is from outside of this forum
        zer0unplanned@friendica.rogueproject.orgZ This user is from outside of this forum
        zer0unplanned@friendica.rogueproject.org
        wrote last edited by
        #18
        @kkarhan @n_dimension @Nonya_Bidniss Nice one!! 😃
        1 Reply Last reply
        0
        • kkarhan@infosec.spaceK kkarhan@infosec.space

          @zer0unplanned @Nonya_Bidniss @n_dimension OFC physically destroying the drives among dozens if not hundreds of identical ones with a physical shredder is also an option, but neither cheap nor fast.

          • But in many cases that is the mandated way to do things to ease off lawyers and in any decent organization CISO & CLO will approve of it if they didn't mandate it already…
          zer0unplanned@friendica.rogueproject.orgZ This user is from outside of this forum
          zer0unplanned@friendica.rogueproject.orgZ This user is from outside of this forum
          zer0unplanned@friendica.rogueproject.org
          wrote last edited by
          #19
          @kkarhan @n_dimension @Nonya_Bidniss No it is slow by design , I copied once the nuke OS of Kodachi OS which is Debian as the scripts are all viewable and copy pasta'able and made an usb with a universal script to nuke any machine once plugged in
          kkarhan@infosec.spaceK 1 Reply Last reply
          0
          • zer0unplanned@friendica.rogueproject.orgZ zer0unplanned@friendica.rogueproject.org
            @kkarhan @n_dimension @Nonya_Bidniss No it is slow by design , I copied once the nuke OS of Kodachi OS which is Debian as the scripts are all viewable and copy pasta'able and made an usb with a universal script to nuke any machine once plugged in
            kkarhan@infosec.spaceK This user is from outside of this forum
            kkarhan@infosec.spaceK This user is from outside of this forum
            kkarhan@infosec.space
            wrote last edited by
            #20

            @zer0unplanned @Nonya_Bidniss @n_dimension yeah, I do want to do something similar with @OS1337 but a bit more precise, aiming fir #LUKS headers first so it'll take literally seconds to make it already non-recoverable.

            zer0unplanned@friendica.rogueproject.orgZ 1 Reply Last reply
            0
            • kkarhan@infosec.spaceK kkarhan@infosec.space

              @zer0unplanned @Nonya_Bidniss @n_dimension yeah, I do want to do something similar with @OS1337 but a bit more precise, aiming fir #LUKS headers first so it'll take literally seconds to make it already non-recoverable.

              zer0unplanned@friendica.rogueproject.orgZ This user is from outside of this forum
              zer0unplanned@friendica.rogueproject.orgZ This user is from outside of this forum
              zer0unplanned@friendica.rogueproject.org
              wrote last edited by
              #21
              @kkarhan @n_dimension @OS1337 @Nonya_Bidniss That is a harder nut, but if you realy want you can even beat up LUKS while I still ask why? that LUKS would be just a key to read overwritten data.
              The aim is the data not the external defences.
              kkarhan@infosec.spaceK 1 Reply Last reply
              0
              • zer0unplanned@friendica.rogueproject.orgZ zer0unplanned@friendica.rogueproject.org
                @kkarhan @n_dimension @OS1337 @Nonya_Bidniss That is a harder nut, but if you realy want you can even beat up LUKS while I still ask why? that LUKS would be just a key to read overwritten data.
                The aim is the data not the external defences.
                kkarhan@infosec.spaceK This user is from outside of this forum
                kkarhan@infosec.spaceK This user is from outside of this forum
                kkarhan@infosec.space
                wrote last edited by
                #22

                @zer0unplanned @Nonya_Bidniss @n_dimension Mostly because deleting/overwriting the header first is extremely fast and twarts any unauthorized data recovery early on.

                • This is a real security concern in #finance, where #ITsec literally has to deal with "Red Army Faction"-style hodtage taking scenarios as part of regulator-mandated #OpSec.
                  • Like "How can access of CxO's be revoked in K&R scenarios?" is a question @BaFin and others ask not just since #wirecard went "poof!"…

                Just because a business doesn't have a shitton of cash at hand and banks neither doesn't mean that armed robbers would necessarily understand, much less accept.

                • Similarly one may need to transit sensitive data but has to safeguard it against unauthorized access no matter the party accessing whilst providing plausible cooperation of it.
                  • Or not having the keys on the storage media entirely.
                kkarhan@infosec.spaceK 1 Reply Last reply
                0
                • kkarhan@infosec.spaceK kkarhan@infosec.space

                  @zer0unplanned @Nonya_Bidniss @n_dimension Mostly because deleting/overwriting the header first is extremely fast and twarts any unauthorized data recovery early on.

                  • This is a real security concern in #finance, where #ITsec literally has to deal with "Red Army Faction"-style hodtage taking scenarios as part of regulator-mandated #OpSec.
                    • Like "How can access of CxO's be revoked in K&R scenarios?" is a question @BaFin and others ask not just since #wirecard went "poof!"…

                  Just because a business doesn't have a shitton of cash at hand and banks neither doesn't mean that armed robbers would necessarily understand, much less accept.

                  • Similarly one may need to transit sensitive data but has to safeguard it against unauthorized access no matter the party accessing whilst providing plausible cooperation of it.
                    • Or not having the keys on the storage media entirely.
                  kkarhan@infosec.spaceK This user is from outside of this forum
                  kkarhan@infosec.spaceK This user is from outside of this forum
                  kkarhan@infosec.space
                  wrote last edited by
                  #23

                  @zer0unplanned @Nonya_Bidniss @n_dimension Either way, comitting "#AssetDenial" is more often than not necessary and one may only have a few seconds before those exercising force may realize that a "duress code" was used and going for the #LUKS headers first may be the only feasible option in a short time...

                  zer0unplanned@friendica.rogueproject.orgZ 1 Reply Last reply
                  0
                  • kkarhan@infosec.spaceK kkarhan@infosec.space

                    @zer0unplanned @Nonya_Bidniss @n_dimension Either way, comitting "#AssetDenial" is more often than not necessary and one may only have a few seconds before those exercising force may realize that a "duress code" was used and going for the #LUKS headers first may be the only feasible option in a short time...

                    zer0unplanned@friendica.rogueproject.orgZ This user is from outside of this forum
                    zer0unplanned@friendica.rogueproject.orgZ This user is from outside of this forum
                    zer0unplanned@friendica.rogueproject.org
                    wrote last edited by
                    #24
                    @kkarhan @n_dimension @Nonya_Bidniss I'll try to do the same on an atomic image of fedora 43 as a pawn image in a box and will tell you if it worked with results. But need a 2nd fedora Atomic SilverBlue on that as a real challenge.
                    The years of me using Kali was very long ago just after backtrack, then I used Parrot OS rather but that all does not mater as it is all Debian RHEL
                    My os is immuatble with a rollback option> makes it very much trickier
                    1 Reply Last reply
                    0
                    • zer0unplanned@friendica.rogueproject.orgZ zer0unplanned@friendica.rogueproject.org
                      @n_dimension @kkarhan @Nonya_Bidniss there are scripts that nuke the whole OS and Kernel and DD, just 1 script to run on the pc .
                      Mr Robot used the chip for a microwave and pierced a hole in the HDD, in the movie whoami they used acid indeed with a mask on.
                      But just 1 script and you can overwrite the hdd or SDD or/and nuke the whole OS> I wish them good luck with that recovering anything.
                      n_dimension@infosec.exchangeN This user is from outside of this forum
                      n_dimension@infosec.exchangeN This user is from outside of this forum
                      n_dimension@infosec.exchange
                      wrote last edited by
                      #25

                      @zer0unplanned @kkarhan @Nonya_Bidniss

                      Problem with SSD "overwrite" is SSDs balance the writes.
                      So if your file is in A D J, SSD MAY balance the write to B E K to balance the cells.

                      On the upside, SSD has one addressable cell, not a fuzzy magnetic dust.

                      zer0unplanned@friendica.rogueproject.orgZ 1 Reply Last reply
                      1
                      0
                      • n_dimension@infosec.exchangeN n_dimension@infosec.exchange

                        @zer0unplanned @kkarhan @Nonya_Bidniss

                        Problem with SSD "overwrite" is SSDs balance the writes.
                        So if your file is in A D J, SSD MAY balance the write to B E K to balance the cells.

                        On the upside, SSD has one addressable cell, not a fuzzy magnetic dust.

                        zer0unplanned@friendica.rogueproject.orgZ This user is from outside of this forum
                        zer0unplanned@friendica.rogueproject.orgZ This user is from outside of this forum
                        zer0unplanned@friendica.rogueproject.org
                        wrote last edited by
                        #26
                        @n_dimension @kkarhan @Nonya_Bidniss So my HDD overwrite are useless on SSD?
                        1 Reply Last reply
                        1
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • World
                        • Users
                        • Groups