Live data from Hacker News

FreeBSD coming to DigitalOcean

digitalocean.uservoice.com

1–10 of 13 posts

Re: FreeBSD coming to DigitalOcean

#3
I would definitely sign up for a FreeBSD droplet, I haven't found a *BSD VPS anywhere near what I'm paying comparable to the specs of a couple OpenVZ Debian GNU/Linux nodes (512MB Ram/50Gb Disk/2TB net) $15/yr. I would hope OpenBSD adoption would soon follow to host many of my services in a more default hardened OS.

Re: FreeBSD coming to DigitalOcean

#4
The key part is the last sentence:

"In regards to FreeBSD, we’ve begun the work necessary to get it supported in DO. We’ve already begun testing it internally and hope to launch within the next 2 months."

Finally!

Re: FreeBSD coming to DigitalOcean

#5
post #4

The key part is the last sentence: "In regards to FreeBSD, we’ve begun the work necessary to get it supported in DO. We’ve already begun testing it internally and hope to launch within the next 2 months." Finally!

Yeah at first its a lot to read but at least it gets to it at the end :)

Re: FreeBSD coming to DigitalOcean

#6

I would definitely sign up for a FreeBSD droplet, I haven't found a *BSD VPS anywhere near what I'm paying comparable to the specs of a couple OpenVZ Debian GNU/Linux nodes (512MB Ram/50Gb Disk/2TB net) $15/yr. I would hope OpenBSD adoption would soon follow to host many of my services in a more default hardened OS.

Er, seems odd to be using OpenVZ if security/hardening is what you're after.

The shared kernel is a larger attack surface compared to KVM or Xen, and the OpenVZ host admin can easily see/manipulate your running processes.

No hate for OpenVZ though, I've used it constantly for about 4 years, but it makes me nervous when its discussed in a multi-tenant context.

Re: FreeBSD coming to DigitalOcean

#7
post #6

I would definitely sign up for a FreeBSD droplet, I haven't found a *BSD VPS anywhere near what I'm paying comparable to the specs of a couple OpenVZ Debian GNU/Linux nodes (512MB Ram/50Gb Disk/2TB net) $15/yr. I would hope OpenBSD adoption would soon follow to host many of my services in a more default hardened OS.

Er, seems odd to be using OpenVZ if security/hardening is what you're after. The shared kernel is a larger attack surface compared to KVM or Xen, and the OpenVZ host admin can easily see/manipulate your running processes. No hate for OpenVZ though, I've used it constantly for about 4 years, but it makes me nervous when its discussed in a multi-tenant context.

ah indeed.. security isn't my focus on those nodes, running a couple of test server applications.

Re: FreeBSD coming to DigitalOcean

#8
I used to have a Linux VM on DigitalOcean. At times it became unreachable, there were some downtimes here and there. I decided to go back to FreeBSD (I used to have a FreeBSD VM on John Companies), and did some research. Vultr.com came up at the top, so I moved to them. Two months in, so far so good.

Re: FreeBSD coming to DigitalOcean

#9
post #6

I would definitely sign up for a FreeBSD droplet, I haven't found a *BSD VPS anywhere near what I'm paying comparable to the specs of a couple OpenVZ Debian GNU/Linux nodes (512MB Ram/50Gb Disk/2TB net) $15/yr. I would hope OpenBSD adoption would soon follow to host many of my services in a more default hardened OS.

Er, seems odd to be using OpenVZ if security/hardening is what you're after. The shared kernel is a larger attack surface compared to KVM or Xen, and the OpenVZ host admin can easily see/manipulate your running processes. No hate for OpenVZ though, I've used it constantly for about 4 years, but it makes me nervous when its discussed in a multi-tenant context.

Why do you think a shared kernel is somehow more secure than a hypervisor?

Re: FreeBSD coming to DigitalOcean

#10
post #9
post #6

Earlier quoted context omitted.

Er, seems odd to be using OpenVZ if security/hardening is what you're after. The shared kernel is a larger attack surface compared to KVM or Xen, and the OpenVZ host admin can easily see/manipulate your running processes. No hate for OpenVZ though, I've used it constantly for about 4 years, but it makes me nervous when its discussed in a multi-tenant context.

Why do you think a shared kernel is somehow more secure than a hypervisor?

Me? My point was that HV/PV virtualization is likely to be more secure than OpenVZ, sorry if it was unclear.
Post reply on HN