The next step is to update documentation and submit updates to the patches they have already submitted upstream to FreeBSD. ASLR is the first step in a long list of exploit mitigation technologies HardenedBSD plans to implement.
Other findings released today include preliminary indications that Pluto's atmospheric pressure has dropped sharply from early observations. This may indicate that the atmosphere is in the process of freezing and falling to Pluto's surface. Finally, new close-up pictures of the surface transmitted back to Earth show direct evidence of nitrogen ice floes reminiscent of glacier movement on Earth. The dwarf planet also seems to be rich in methane ice and carbon dioxide ice.
Because we are in a scientific domain, most of our customers use Open Source software alongside our product. We also maintain Open Source projects and directly support others. We're strong supporters of Open Source and understand the value of having access to the source code.
We also support a free (as in beer) version of the software with a smaller feature set (production and enterprise elements that individual users don't need are removed). We'd like that version to use the same model as well to give users that don't need the full commercial version the ability to extend the software and submit patches back to us for inclusion in future releases.
Overall, we'd really like to find a model that allows our core product to work more like an Open Source product while maintaining control over the distribution rights. We'd like to foster a community around the product but still generate revenue to fund it. In our space, the "give the product away but pay for support" model has never really worked. The market is too small and, importantly, most customers understand our value proposition and have no problem with our annual license model.
We've looked at traditional dual licensing approaches, but don't think they're really right fit, either. A single license that gives users access to the code but limits the ability to redistribute the code and distribute patches to the "core" is what we'd prefer. My questions for the Slashdot community: Does anyone have direct experience with models like this? Are there existing licenses that we should look at? What companies have succeeded doing this? Who has failed?
One possible explanation being discussed at DLR's Lander Control Center is that the position of Philae may have shifted slightly, perhaps by changing its orientation with respect to the surface in its current location. The lander is likely situated on uneven terrain, and even a slight change in its position – perhaps triggered by gas emission from the comet – could mean that its antenna position has also now changed with respect to its surroundings. This could have a knock-on effect as to the best position Rosetta needs to be in to establish a connection with the lander.
The current status of Philae remains uncertain and is a topic of on-going discussion and analysis. But in the meantime, further commands are being prepared and tested to allow Philae to re-commence operations. The lander team wants to try to activate a command block that is still stored in Philae's computer and which was already successfully performed after the lander's unplanned flight across to the surface to its final location. "Although the mission will now focus its scientific priority on the orbiter, Rosetta will continue attempting – up to and past perihelion – to obtain Philae science packets once a stable link has been acquired," adds Patrick Martin, Rosetta mission manager.