3 ms·

Last time I tried the full disk encyrption [sic] it was an awful setup compared to Linux. > https://why-openbsd.rocks/fact/meltdown-spectre/ https://why-openbs

Last time I tried the full disk encyrption [sic] it was an awful setup compared to Linux. > https://why-openbsd.rocks/fact/meltdown-spectre/ https://why-openbsd.rocks/fact/meltdown-spectre/ Uh, yeah. They did that, just like Linux did before them. I especially like the reply to the announcement that was "uh… I hope you didn't spend these two months coming up with that solution. We already did that for Linux, so you could have just asked".

zolotarev 8y ago
Now full disk encryption is pretty simple: https://rgz.ee/openbsd/install.html https://rgz.ee/openbsd/install.html
- knorker 8y ago
  That's very relative. Sure, it does look better now, and I'm fine with this setup being a bit annoying since it's a one-time thing.
aquabeagle 8y ago
Just because the idea is known doesn't make it trivial to implement in a completely different kernel.
- knorker 8y ago
  I think you misunderstood my whole point. It appears that OpenBSD chose to spend months starting from scratch researching exactly what needed to be mapped in virtual memory, instead of just confirming the x86/x64 platform needs that were already researched and published by that time.
johnr2 8y ago
> They did that, just like Linux did before them. I especially like the reply to the announcement that was "uh… I hope you didn't spend these two months coming up with that solution. We already did that for Linux, so you could have just asked". Linux developers were told about meltdown/spectre right away, but OpenBSD wasn't told until the end of the embargo over two months later. https://www.itwire.com/security/81338-handling-of-cpu-bug-disclosure-incredibly-bad-openbsd-s-de-raadt.html https://www.itwire.com/security/81338-handling-of-cpu-bug-di...
- knorker 8y ago
  I think you misunderstood my whole point. It appears that OpenBSD chose to spend months starting from scratch researching exactly what needed to be mapped in virtual memory, instead of just confirming the x86/x64 platform needs that were already researched and published by that time. I'm not talking about the two months (or whatever it was) Linux had as head start. I'm talking about the post-publication ~two months.

zolotarev 8y ago

Now full disk encryption is pretty simple: https://rgz.ee/openbsd/install.html https://rgz.ee/openbsd/install.html

knorker 8y ago
That's very relative. Sure, it does look better now, and I'm fine with this setup being a bit annoying since it's a one-time thing.

aquabeagle 8y ago

Just because the idea is known doesn't make it trivial to implement in a completely different kernel.

knorker 8y ago
I think you misunderstood my whole point. It appears that OpenBSD chose to spend months starting from scratch researching exactly what needed to be mapped in virtual memory, instead of just confirming the x86/x64 platform needs that were already researched and published by that time.

johnr2 8y ago

> They did that, just like Linux did before them. I especially like the reply to the announcement that was "uh… I hope you didn't spend these two months coming up with that solution. We already did that for Linux, so you could have just asked". Linux developers were told about meltdown/spectre right away, but OpenBSD wasn't told until the end of the embargo over two months later. https://www.itwire.com/security/81338-handling-of-cpu-bug-disclosure-incredibly-bad-openbsd-s-de-raadt.html https://www.itwire.com/security/81338-handling-of-cpu-bug-di...

knorker 8y ago
I think you misunderstood my whole point. It appears that OpenBSD chose to spend months starting from scratch researching exactly what needed to be mapped in virtual memory, instead of just confirming the x86/x64 platform needs that were already researched and published by that time. I'm not talking about the two months (or whatever it was) Linux had as head start. I'm talking about the post-publication ~two months.