The Secure Public Data Repository?
jducoeur writes "So Hailstorm has died an unlamented death. But the demand for the idea of an information repository isn't going to go away -- users demand convenience, and this would be convenient. So here's a timely question looking for wild speculation: how would a truly secure, public data repository work? How would your data be stored? Would it be centralized or distributed? How would you grant access to specific elements within it? What would the business case for running such an archive be? Maybe if we can come up with a good design now, we can head off the next inevitable bad one..."
The Oceanstore project at Berkeley is aiming to do just that: create a distributed storage model to provide a global, distributed, persistant storage resource.
Test your net with Netalyzr
As per many other postings here on /., we're hoping to make oNumber.net a user controlled central repository. You create your entry, you manage it, you control who gets to see what and you can delete your listing anytime. There are built in features such as the SPACECARD and Resume generator that make it useful on it's own. People access your SPACECARD using the unique oNumber that identifies your entry.
O'WONDERWe're working on it.
- User authentication and authorization across multiple trust domains
- Automated exchange, management, and auditing of consumer information, based on permissions and in compliance with government regulations
- Automated customer registration and updating
- Automated management of public key infrastructure security solutions
- Synchronization of permissions, entitlements, and other context-based user information
They were fairly actively seeking clients during the Bubble Years, but understandably things are not rolling along so well these days. Anyone care to comment on what is available at their site? It seems to implement everything people say they want in a single-signon solution. That's probably why it hasn't been widely adopted, too much control is given to the owner of the information (that'd be YOU).Edith Keeler Must Die
Microsoft announced that they were deferring for the time being the idea of Hailstorm as a fully, explicitly Microsoft-controlled depository in direct competition with their customers. They did not say that Hailstorm was going away, merely that it would now be broken up into multiple repositories managed in partnership with their customers (e.g. large banks and e-commerce sites). Which is not to say that (a) the concept no longer exists (b) the aggregate total will not be under Microsoft's control (c) they might not revive the central repository idea in the future.
sPh
putfwd.com - 1GB Free file storage with a twist
However, their technology is deeply flawed, not just in an engineering sense but also a legal one: it is tied down by patents and IP disputes, and their system is essentially centralised.
They also have almost nobody on board at all, you can get an XNS "agent" but not use it anywhere. The technology is ludicrously complicated, hidden behind masses of white papers that don't really tell you what to do in order to make an implementation.