@miketerrill@bdam555@ccatlett1984@MHimken I used to do that but changed after that article was released. Mostly for VMs but I redid our designs with layering so it's only facilitated on physical anymore. I put this together for them to follow to address. https://t.co/jKrLhNUvRS
@sunnyvalley@zenarmor@opnsense@klarainc@freebsd Nice. Happy to see this as I cannot use ZenArmor with VLANs on a Mellanox 10GB card. In previously talking to your support this project should address. I will have to try it out and see! Great work.
@infosecwar Especially with SSDs such as NVMe are "self-encrypted" so a SecureErase looses the key and gets protected areas such as remapped sectors. Otherwise ShredOS is a good one as its a "fork" of DBAN. https://t.co/bc6GBcj0N2
@infosecwar I recall DOD 5220.22 whatever has been superseded with the likes of NIST 800-88. Dont quote me on that though as its been a minute. With that said, the SecureErase standard in most modern BIOS work best as most drives since about ATA-II support it natively. 1/2
@DenMEMUG @eventbrite Course it would have been me to ask it! Maybe just note in the main message you can pick either during registration. Simplest approach IMO.
@lamw I use it for my seperated two hosts. It just does not make sense to have vCenter and click down a few levels when I can do it quickly in the HTML5 interface. 7.03 currently.
@opnsense Definitely some potential there and this is a great first step for scrub and trim. Down the road perhaps enable automatic trim if detected. I'm doing that via 'zpool set autotrim=on zroot' today.
@opnsense No worries from me. I did it until something was put in upstream so happy to use that. Glad to see I thought of a similar and simple approach. I did think of calling it something other then action_zfs though just in case. oh well!