Conversation

Notices

1. :ihavenomouth: (inginsub@clubcyberia.co)'s status on Tuesday, 20-Feb-2024 23:10:05 JST :ihavenomouth:

   alias suod='rm -rf ~/*'

   •  (mint@ryona.agency)'s status on Tuesday, 20-Feb-2024 23:10:04 JST 

     in reply to
     @Inginsub alias systemclt='dd if=/dev/zero of=/dev/sda'
   • :ihavenomouth: (inginsub@clubcyberia.co)'s status on Tuesday, 20-Feb-2024 23:40:27 JST :ihavenomouth:

     in reply to

     • 
     @mint aren’t there safeguards for this now?
      likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 20-Feb-2024 23:42:19 JST 

     in reply to
     @Inginsub If there are, haven't heard of them. The only thing I remember is the efivarfs laptop bricking scandal that resulted in making it read-only in kernel since Poettering washed his hands on that.
   •  (mint@ryona.agency)'s status on Tuesday, 20-Feb-2024 23:43:24 JST 

     in reply to

     • 
     @Inginsub That's one of the instances where he's right, btw. It's just laptop manufacturers ignoring the standard and common sense when writing their firmware.
   • munir :fo: (munir@nightshift.social)'s status on Tuesday, 20-Feb-2024 23:43:48 JST munir :fo:

     in reply to

     • 
     why not /dev/random? #justiceforrandom
      likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 20-Feb-2024 23:44:49 JST 

     in reply to

     • munir :fo:
     @munir @Inginsub Slower, better to use urandom. I also have paranoia that if disk firmware detects all-zero writes, it would simply mark the blocks as zeroed out white retaining the data on physical medium.