What is the accelerate method of free space wiping with random fill?How to know the progress of sfill free...

An inequality of matrix norm

Why doesn't the EU now just force the UK to choose between referendum and no-deal?

Use void Apex method in Lightning Web Component

How can I track script which gives me "command not found" right after the login?

(Calculus) Derivative Thinking Question

How Could an Airship Be Repaired Mid-Flight

It's a yearly task, alright

Why is the President allowed to veto a cancellation of emergency powers?

Most cost effective thermostat setting: consistent temperature vs. lowest temperature possible

Brexit - No Deal Rejection

Gravity magic - How does it work?

Have researchers managed to "reverse time"? If so, what does that mean for physics?

Opacity of an object in 2.8

What's the meaning of “spike” in the context of “adrenaline spike”?

Employee lack of ownership

Interplanetary conflict, some disease destroys the ability to understand or appreciate music

How to terminate ping <dest> &

Are there other languages, besides English, where the indefinite (or definite) article varies based on sound?

How to read the value of this capacitor?

What exactly is this small puffer fish doing and how did it manage to accomplish such a feat?

How big is a MODIS 250m pixel in reality?

How to write cleanly even if my character uses expletive language?

Why one should not leave fingerprints on bulbs and plugs?

If I can solve Sudoku can I solve Travelling Salesman Problem(TSP)? If yes, how?



What is the accelerate method of free space wiping with random fill?


How to know the progress of sfill free space wiping process?Why does the total space used on my hard drive not reflect what Disk Usage Analyzer Says?Meaning of the free space indication in DelugePartitioning with Windows 7, no free spaceAfter uninstalling wine some of the free space is 'locked'?How does the automatic installation work with free space?What is the safest method for repartitioning space from the / partition?No more disk space: How can I find what is taking up the space?How to know the progress of sfill free space wiping process?Wiping free disk space by deleting large amount of files regularly?Free space in my laptop with Ubuntu 18.04 preinstalled













1















I am currently using sfill to wipe free space in my root partition ( /dev/sdaX). Its default setting is a 38 pass sudo sfill -v / but its taking hours to complete this step. I then tried to use less secure three pass method sudo sfill -lv / the problem is its taking fairly the same amount of time to wipe free space as the default. It is due to dev/urandom which peaks at 13MB/s. While searching for an alterntive method to speed up free space wiping step, I reached this link which uses openssl to randomize the wipe.



 openssl rand $(</proc/partitions awk '$4=="sda" {print $3*1024}') >/dev/sda


Is this a good way to wipe free space in root drive or other safer method exists? In the above command sda is our root partion sdaX, right?










share|improve this question




















  • 1





    On my machine dd if=/dev/urandom bs=1M count=1000 | pv >/dev/null shows that /dev/urandom runs at least at 170MB/s (about 5 seconds/GB). dd if=/dev/urandom bs=1M of=/somebigfile is about as fast as you can get.

    – xenoid
    Apr 14 '18 at 7:01


















1















I am currently using sfill to wipe free space in my root partition ( /dev/sdaX). Its default setting is a 38 pass sudo sfill -v / but its taking hours to complete this step. I then tried to use less secure three pass method sudo sfill -lv / the problem is its taking fairly the same amount of time to wipe free space as the default. It is due to dev/urandom which peaks at 13MB/s. While searching for an alterntive method to speed up free space wiping step, I reached this link which uses openssl to randomize the wipe.



 openssl rand $(</proc/partitions awk '$4=="sda" {print $3*1024}') >/dev/sda


Is this a good way to wipe free space in root drive or other safer method exists? In the above command sda is our root partion sdaX, right?










share|improve this question




















  • 1





    On my machine dd if=/dev/urandom bs=1M count=1000 | pv >/dev/null shows that /dev/urandom runs at least at 170MB/s (about 5 seconds/GB). dd if=/dev/urandom bs=1M of=/somebigfile is about as fast as you can get.

    – xenoid
    Apr 14 '18 at 7:01
















1












1








1








I am currently using sfill to wipe free space in my root partition ( /dev/sdaX). Its default setting is a 38 pass sudo sfill -v / but its taking hours to complete this step. I then tried to use less secure three pass method sudo sfill -lv / the problem is its taking fairly the same amount of time to wipe free space as the default. It is due to dev/urandom which peaks at 13MB/s. While searching for an alterntive method to speed up free space wiping step, I reached this link which uses openssl to randomize the wipe.



 openssl rand $(</proc/partitions awk '$4=="sda" {print $3*1024}') >/dev/sda


Is this a good way to wipe free space in root drive or other safer method exists? In the above command sda is our root partion sdaX, right?










share|improve this question
















I am currently using sfill to wipe free space in my root partition ( /dev/sdaX). Its default setting is a 38 pass sudo sfill -v / but its taking hours to complete this step. I then tried to use less secure three pass method sudo sfill -lv / the problem is its taking fairly the same amount of time to wipe free space as the default. It is due to dev/urandom which peaks at 13MB/s. While searching for an alterntive method to speed up free space wiping step, I reached this link which uses openssl to randomize the wipe.



 openssl rand $(</proc/partitions awk '$4=="sda" {print $3*1024}') >/dev/sda


Is this a good way to wipe free space in root drive or other safer method exists? In the above command sda is our root partion sdaX, right?







security disk-usage openssl storage secure-erase






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 6 mins ago









Pablo Bianchi

2,94521535




2,94521535










asked Apr 14 '18 at 5:42









EkaEka

1,05862139




1,05862139








  • 1





    On my machine dd if=/dev/urandom bs=1M count=1000 | pv >/dev/null shows that /dev/urandom runs at least at 170MB/s (about 5 seconds/GB). dd if=/dev/urandom bs=1M of=/somebigfile is about as fast as you can get.

    – xenoid
    Apr 14 '18 at 7:01
















  • 1





    On my machine dd if=/dev/urandom bs=1M count=1000 | pv >/dev/null shows that /dev/urandom runs at least at 170MB/s (about 5 seconds/GB). dd if=/dev/urandom bs=1M of=/somebigfile is about as fast as you can get.

    – xenoid
    Apr 14 '18 at 7:01










1




1





On my machine dd if=/dev/urandom bs=1M count=1000 | pv >/dev/null shows that /dev/urandom runs at least at 170MB/s (about 5 seconds/GB). dd if=/dev/urandom bs=1M of=/somebigfile is about as fast as you can get.

– xenoid
Apr 14 '18 at 7:01







On my machine dd if=/dev/urandom bs=1M count=1000 | pv >/dev/null shows that /dev/urandom runs at least at 170MB/s (about 5 seconds/GB). dd if=/dev/urandom bs=1M of=/somebigfile is about as fast as you can get.

– xenoid
Apr 14 '18 at 7:01












1 Answer
1






active

oldest

votes


















1














First and foremost, wiping your drive 35+ times is completely unnecessary. The Guttmann Method (35 wipes) is something designed to wipe any drive, from brand-new modern spinning drives to massive ancient 5MB behemoths that are more likely to store resident data. With that said, wiping your drive once or twice is pretty much the best you can do. You have a modern magnetic drive.



The sfill command is... silly. See the manpage for what I mean. If you only need to wipe the drive out with zeros, you can just use the (far simpler) sfill -llz / to wipe out all free space with zeros, once. This (according to Guttmann himself, see above link as well as right here) is more than good enough for the vast majority of systems. As you're writing zeros instead of random data, your only speed limit will be your drive's speed.



If you need plausible deniability ("No, officer, I didn't wipe this hard drive"), you can use the sister command sfill -ll / to wipe your drive in a single pass with random data. This will be slower, but just as secure for your system as any other wiping method with the addition of possible plausible deniability.



However, if you really need to ensure that no data is absolutely recoverable from this drive (in theory or otherwise), use a drill.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024864%2fwhat-is-the-accelerate-method-of-free-space-wiping-with-random-fill%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    First and foremost, wiping your drive 35+ times is completely unnecessary. The Guttmann Method (35 wipes) is something designed to wipe any drive, from brand-new modern spinning drives to massive ancient 5MB behemoths that are more likely to store resident data. With that said, wiping your drive once or twice is pretty much the best you can do. You have a modern magnetic drive.



    The sfill command is... silly. See the manpage for what I mean. If you only need to wipe the drive out with zeros, you can just use the (far simpler) sfill -llz / to wipe out all free space with zeros, once. This (according to Guttmann himself, see above link as well as right here) is more than good enough for the vast majority of systems. As you're writing zeros instead of random data, your only speed limit will be your drive's speed.



    If you need plausible deniability ("No, officer, I didn't wipe this hard drive"), you can use the sister command sfill -ll / to wipe your drive in a single pass with random data. This will be slower, but just as secure for your system as any other wiping method with the addition of possible plausible deniability.



    However, if you really need to ensure that no data is absolutely recoverable from this drive (in theory or otherwise), use a drill.






    share|improve this answer




























      1














      First and foremost, wiping your drive 35+ times is completely unnecessary. The Guttmann Method (35 wipes) is something designed to wipe any drive, from brand-new modern spinning drives to massive ancient 5MB behemoths that are more likely to store resident data. With that said, wiping your drive once or twice is pretty much the best you can do. You have a modern magnetic drive.



      The sfill command is... silly. See the manpage for what I mean. If you only need to wipe the drive out with zeros, you can just use the (far simpler) sfill -llz / to wipe out all free space with zeros, once. This (according to Guttmann himself, see above link as well as right here) is more than good enough for the vast majority of systems. As you're writing zeros instead of random data, your only speed limit will be your drive's speed.



      If you need plausible deniability ("No, officer, I didn't wipe this hard drive"), you can use the sister command sfill -ll / to wipe your drive in a single pass with random data. This will be slower, but just as secure for your system as any other wiping method with the addition of possible plausible deniability.



      However, if you really need to ensure that no data is absolutely recoverable from this drive (in theory or otherwise), use a drill.






      share|improve this answer


























        1












        1








        1







        First and foremost, wiping your drive 35+ times is completely unnecessary. The Guttmann Method (35 wipes) is something designed to wipe any drive, from brand-new modern spinning drives to massive ancient 5MB behemoths that are more likely to store resident data. With that said, wiping your drive once or twice is pretty much the best you can do. You have a modern magnetic drive.



        The sfill command is... silly. See the manpage for what I mean. If you only need to wipe the drive out with zeros, you can just use the (far simpler) sfill -llz / to wipe out all free space with zeros, once. This (according to Guttmann himself, see above link as well as right here) is more than good enough for the vast majority of systems. As you're writing zeros instead of random data, your only speed limit will be your drive's speed.



        If you need plausible deniability ("No, officer, I didn't wipe this hard drive"), you can use the sister command sfill -ll / to wipe your drive in a single pass with random data. This will be slower, but just as secure for your system as any other wiping method with the addition of possible plausible deniability.



        However, if you really need to ensure that no data is absolutely recoverable from this drive (in theory or otherwise), use a drill.






        share|improve this answer













        First and foremost, wiping your drive 35+ times is completely unnecessary. The Guttmann Method (35 wipes) is something designed to wipe any drive, from brand-new modern spinning drives to massive ancient 5MB behemoths that are more likely to store resident data. With that said, wiping your drive once or twice is pretty much the best you can do. You have a modern magnetic drive.



        The sfill command is... silly. See the manpage for what I mean. If you only need to wipe the drive out with zeros, you can just use the (far simpler) sfill -llz / to wipe out all free space with zeros, once. This (according to Guttmann himself, see above link as well as right here) is more than good enough for the vast majority of systems. As you're writing zeros instead of random data, your only speed limit will be your drive's speed.



        If you need plausible deniability ("No, officer, I didn't wipe this hard drive"), you can use the sister command sfill -ll / to wipe your drive in a single pass with random data. This will be slower, but just as secure for your system as any other wiping method with the addition of possible plausible deniability.



        However, if you really need to ensure that no data is absolutely recoverable from this drive (in theory or otherwise), use a drill.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 31 '18 at 15:50









        Kaz WolfeKaz Wolfe

        26.1k1376136




        26.1k1376136






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024864%2fwhat-is-the-accelerate-method-of-free-space-wiping-with-random-fill%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

            Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

            Should I use Docker or LXD?How to cache (more) data on SSD/RAM to avoid spin up?Unable to get Windows File...