On 06/13/2013 12:51 AM, Joseph D. Wagner wrote:
On 06/11/2013 4:36 pm, Pádraig Brady wrote:
On 06/11/2013 07:20 AM, Joseph D. Wagner wrote:
Currently, when --remove (-u) is specified, shred overwrites the file
name once for each character, so a file name of 0123456789 would be
overridden
On 06/13/2013 8:35 am, Pádraig Brady wrote:
On 06/13/2013 12:51 AM, Joseph D. Wagner wrote:
## perchar ##
real678m33.468s
user0m9.450s
sys3m20.001s
## once ##
real151m54.655s
user0m3.336s
sys0m32.357s
## none ##
real107m34.307s
user0m2.637s
sys0m21.825s
On 06/11/2013 4:36 pm, Pádraig Brady wrote:
On 06/11/2013 07:20 AM, Joseph D. Wagner wrote:
Currently, when --remove (-u) is specified, shred overwrites the file
name once for each character, so a file name of 0123456789 would be
overridden 10 times. While this may be the most secure, it is
Currently, when --remove (-u) is specified, shred overwrites the file
name once for each character, so a file name of 0123456789 would be
overridden 10 times. While this may be the most secure, it is also the
most time consuming as each of the 10 renames has its own fsync. Also,
renaming may not
On 06/11/2013 07:20 AM, Joseph D. Wagner wrote:
Currently, when --remove (-u) is specified, shred overwrites the file
name once for each character, so a file name of 0123456789 would be
overridden 10 times. While this may be the most secure, it is also the
most time consuming as each of the 10
