I don't understand this thinking. The GPL is more restrictive than the FreeBSD license. You have more freedoms with the FreeBSD license than you do with the GPL(of any version).
> I wish FreeBSD held the position Linux does in the market today. That would be heaven.
Well The BSD's were embattled with a lawsuit from AT&T at the time Linux came around, so it got a late start as it were, even if it's a lot older.
probably because OpenBSD developers use laptops, so they port the OS to laptops all the time.
FreeBSD has a few laptop developers, but most are doing server work. There is a project currently underway to help get more laptops back into support again: https://github.com/FreeBSDFoundation/proj-laptop
The kernel guarantees that once restricted, that process will stay restricted. The only way for it to un-restrict itself would be to also compromise the Linux kernel. So you have 2 things you have to compromise to own the machine, instead of just 1.
Yes, but basically nobody uses either of those things. Some vendors like Redhat enables some of it by default, but when people have issues getting software to work, the first thing they are told to try is to turn all that stuff off.
Which means in the real world, the likelihood of that stuff being on and secure is fairly low, but not zero.
With landlock, pledge/unveil and similar tech, the developers of the software write and configure it, it's on by default and probably can't be turned off(or at least not easily).
The opposite is true. Containwrization systems were built into operating systems as security features. The whole “Linux packaging is a hellscape of self-induced problems, so let’s duct tape a squashfs onto the side of this new security isolation system and call it a deployment primitive” use case we now call “containers” came later and is a fairly inelegant and wasteful way to avoid needing to solve the packaging hellscape problem. It’s valuable to many! But definitely is the square peg to the round hole (security isolation layer) of setns and chroot and friends.
You can make containers mostly as hardened security wise as a VM (but generally none of that comes by default), the big thing you can't get that a VM gives you is a new kernel instance. In a VM you have to break 2 kernels to totally own a machine.
In a container, provided the container software doesn't do it for you(which is likely true), you just have to break 1 kernel.
OH I think I finally understand your comment... I think you are confusing FreeBSD jails/Solaris Zones with containers. They are not the same things. Containers for instance exist on FreeBSD now, as a totally different thing than FreeBSD Jails.
Jails/Zones are definitely security features. That's not the case for Containers(popularized via Docker).
The technologies that enabled containerization (namespaces, chroot, and cgroups, and their predecessors on BSD/Solaris) were created specifically for security and resource isolation.
The people who came up with "containers" as we know them today found a clever hack: combining those security-oriented tools with a filesystem-in-a-box and packaging system allowed people to package entire OS userlands and run them pretty deterministically in multiple places. The security isolation properties of namespaces/cgroups/chroot also happened to provide increased determinism.
And I'm not criticizing that; containers are a very clever hack that solved a problem a lot of people have. I use them every day.
That said, the fact that containers became so ubiquitous in the first place speaks a completely self-induced problem that we didn't need to have in the software engineering community. That problem is, unfortunately, human/incentive-related in nature, so containers are probably the best we're going to get--problem is, they're not that good.
The Outer Space Treaty is very very clear: anything launched into space is the responsibility of the country that launched it. Even if a private company payts for it and operates it, it's still the responsibility of the launching nation. Even if you launch from international waters, your operating company is still registered to a specific country, and the company is made up of citizens of one or more countries, and it is those countries which are responsible for the satellites. Those countries, in fact, have the responsibility to make sure that their citizens follow their laws and regulations. Unless you and your entire team are self-sustaining on that datacenter in outer space (maybe possible a century from now? Maybe not possible ever), you will be hunted down by the proper authorities and held to account for your actions. There is no magic "space is beyond the law" rules; it is just as illegal- and you are just as vulnerable to being arrested- for work done on a datacenter in space as work done on a datacenter on the ground.
Spy satellites maneuver so that no one can tell who launched them, or when. If these satellites can do the same, good luck pinning responsibility on someone on the ground. Hell, with Musk's low orbit network, he could probably even provide connectivity to them in a plausibly-deniable manner.
A data center on an orbit that is only known to the operators makes it difficult to use as a data center in a meaningful way - where do you point your uplink?
Spy satellites are individual craft. Proposals tossed about suggest significant constellates to give sufficient coverage to the land.
Suggestions involving square kilometers of solar power are not exactly things that would be easy to hide.
> Data centers in space. The problem is that data centers take up a ton of space and they need a huge amount of energy. Enter StarCloud. This is the beginning of a future where most new data centers are being built in space. They're starting small, but the goal is to build massive orbital data centers that will make computing more efficient and less of a burden on the limited resources down here on Earth.
These aren't small things. You can't hide it.
> And so we're building with a vision to build extremely large full 40 megawatt data centers. It's about 100 tons. It's what you can fit in one full Starship halo bay.
No, this is not true. First of all, every nation is required by space law to publish the initial orbits of every object they launch, as part of that taking responsibility I mentioned earlier.
The US Government further publishes tracking on pretty much every single thing in orbit of the earth larger than a few centimeters, to help satellite operators avoid space debris. They do obfuscate the current orbit of their own spy satellites (only publishing their initial orbit), but other countries and even private citizens around the world keep obsessive tabs on these things (e.g. https://sattrackcam.blogspot.com/). This sort of thing is easily within the reach of even a medium sized nation state that was interested in the investment: just need a couple of big ole radars and you can do it just like the US does. So if you do try and hide the resources of a nation-state can easily counter.
The solution to oppressive government is not technological, it's political. Prevent countries from going bad, retrieve the ones that have gone bad, it works out a lot better for everyone.
Bitcoin is a great example of something outside of jursidictions. Now look at how much BTC the FBI has seized. In practice, power is gonna power. The US, Russia or China can take out your data centre unless you play by whatever the rules are. If not physically blow up you need to trade, you need a country for ground operations etc. You need a downlink. Being in space meaning no jurisdiction is plain rediculous.
Yes, but you can make assumptions based on what you know about humans generally. Like their example that if you ask if you have long hair. If you answer yes the likelihood is you are probably female.
You can think of all sorts of questions and answers like this, and when you combine with the assumptions and answers from previous answers you can make even more assumptions. They won't always be correct, but you don't have to be "perfect", depending on your use-case. For example for advertising purposes assumptions(even if incorrect) can still go a long way.
There is a reason Target got sooo good at identifying pregnant women[0] before the women knew they were pregnant that they creeped out women, and had to pull back what they did with that information. This was like a decade or more ago. It's only gotten more accurate since then.
Even if that one particular instance is false, I seem to remember Target saying their model was too accurate and they were changing how they did things. i.e. Target admitted to predicting pregnancies very well.
Why would they do that, if they didn't think their system was that good?
Maybe to convince other companies to buy Target ads. Advertising companies uptalk how effective their advertisements are to persuade other companies to buy adspace.
Target isn’t going to do something that scares away consumers, like say “our ad tracking is TOO good”, unless there’s another benefit that makes it net positive for them.
> Target got sooo good at identifying pregnant women
That's why I pay with cash and do not have a loyalty card (other customers often offer theirs at cash register anyway). And of course I don't even go to Target.
I don't know if Target specifically use all of these, but I would bet they have data based on at least some of facial/gait/demographic recognition, wi-fi/Bluetooth beaconing, vehicle registrations, time and location tracking, statistical analysis of your purchases and clustering of people you have made purchases next to (e.g. you bought something at same time and till as your mother more then once). I'm sure they have other methods too. They can also combine datasets from brokers that do have a face:name link (say you used a card at another store that captured it and sold the data) and resolve you within their own data that way.
... for now. The future is unknown. So far republicans seem mostly happy with the uncertainty Trump delivers to the world. What will the next administration be like?
> I wish FreeBSD held the position Linux does in the market today. That would be heaven.
Well The BSD's were embattled with a lawsuit from AT&T at the time Linux came around, so it got a late start as it were, even if it's a lot older.