A filesystem with text search eh? I seem to recall ICL in the UK did one of those (CAFS Content Addressable File System) in 1984 or 5.
Cut to monty python...
1st Hacker: File system with text search? - luxury - the kids of today don't know how good they have it! 2nd Hacker: When I were a lad we had 8 users on a 5mhz 8085. 1st Hacker: Luxury! 8085, we'd have given our souls for an 8085. We had 6502... etc... etc
Sure and there is no operator error either. I had a bunch of machines at a well know hosting company who managed to cut the power despite generators and UPS. There is no accounting for people.
The worst power related problem I've seen came with some RAID arrays that were running a veritas file system. Unfortunately nobody had bothered to enter the full licence into the driver software so they were on a demo license... which had expiered two months before the power outage. Only some quick thinking to call the veritas UK office (who were open at 3am californai time) got the system back up!
The nation of Sealand is composed of a steel and concrete platform anchored to the bottom of the sea off the coast of England, not in the Channel but in the North Sea....
"I can tell you, in no uncertain terms, that the United States does not recognize the Principality of Sealand," - Walter Deering, Miami special agent-in-charge of the Bureau of Diplomatic Security.
There are already data sharing systems that solve this issue without privacy violations.
CyberSource has one (which I helped design) that process cards for lots of merchants - when a new transaction comes in they look at it on a lot of different factors one of which is the history of this person (card/email/phys address/phone#) on other sites - if there has been no problems and it passes the other tests they give back a low score and the transaction happens - if there have been problems they give back a high score; the merchant can then decide what to do next (reject or ask for more info).
In all of this the customers data given to one merchant is never disclosed to another (nor is anything about the customer or their history). It's a basic premis of the system that data goes in but does not come out. It works remarkably well.
CyberSource is at http://www.cybersource.com Disclosure: I used to be CTO at CyberSource (before I retired:-) and I still own a lot of stock.
Another issue is that the cost of approvals (FCC et al) for a production product is not inconsiderable. Publishing a design pushes all the compliance issues onto the builder.
Nice toy though - perhaps they will licence it out like they did the PJB MP3 player (great toy I love mine).
Age & experience = good, age alone = bad
on
Too Old To Code?
·
· Score: 1
I've hired a lot of engineers in my time and I don't think age matters as much as passion and cluefullness.
I've seen kids (less than 20) who get it and people 50+ who get it (didn't have many applicants who were over 50 so it's really hard to tell beyond that). I've also seen people of all ages who were clueless.
A good age mix is often a distinct advantage in a product team as it lets some of the old hands inject some real world wizdom into things. Better products are the result.
I don't buy that Linux is that bad (not compared to people trying to use NT as a firewall). Personally I prefer black box firwalls (I like the pix) but at home I went with BSD (despite growing up writing device drivers for version 7 and system V:-)
I think for most practical purposes the big issue in firewalls is configuration (or lack of) and user stupidity (if users have remote access without hardware authentication then assume the bad guys do too). Add to that an eggshell mentality (hard wall soft middle) and you have a recipie for bad security. If you are a real badguy (as opposed to a script kiddie) social engineering beats software attacks by a wide margin.
I think you are giving TRUSTe a bad rap. It was never intended to be privacy police (I was one of the group of five people who formulated the idea with Lori). Our intent was to codify an informed consent model.
In a free country people get to make choice about how much information the do and don't give away - what TRUSTe seeks to do is give them background to make an informed choice. TRUSTe provides a level of confidence that an organization will keeps it's word - nothing else.
I think where people get upset with this is that it's not an "implicit privacy" model in which all info is protected unless explicit concent is given. An implicit privacy model would probably be a good thing however it's a good first step to shine a light on whatever is already there.
John Pettitt Former CTO Beyond.com & CyberSource (now retired)
Slashdot Mirror
Cut to monty python ...
1st Hacker: File system with text search? - luxury - the kids of today don't know how good they have it! ... etc ... etc
2nd Hacker: When I were a lad we had 8 users on a 5mhz 8085.
1st Hacker: Luxury! 8085, we'd have given our souls for an 8085. We had 6502
The worst power related problem I've seen came with some RAID arrays that were running a veritas file system. Unfortunately nobody had bothered to enter the full licence into the driver software so they were on a demo license ... which had expiered two months before the power outage. Only some quick thinking to call the veritas UK office (who were open at 3am californai time) got the system back up!
Read the full story at http://www.nationalgeo.com /infocentral/answer/gya9903.html
"I can tell you, in no uncertain terms, that the United States does not recognize the Principality of Sealand,"
- Walter Deering, Miami special agent-in-charge of the Bureau of Diplomatic Security.
See also: Source of quote
There are already data sharing systems that solve this issue without privacy violations.
:-) and I still own a lot of stock.
CyberSource has one (which I helped design) that process cards for lots of merchants - when a new transaction comes in they look at it on a lot of different factors one of which is the history of this person (card/email/phys address/phone#) on other sites - if there has been no problems and it passes the other tests they give back a low score and the transaction happens - if there have been problems they give back a high score; the merchant can then decide what to do next (reject or ask for more info).
In all of this the customers data given to one merchant is never disclosed to another (nor is anything about the customer or their history). It's a basic premis of the system that data goes in but does not come out. It works remarkably well.
CyberSource is at http://www.cybersource.com
Disclosure: I used to be CTO at CyberSource (before I retired
Another issue is that the cost of approvals (FCC et al) for a production product is not inconsiderable. Publishing a design pushes all the compliance issues onto the builder.
Nice toy though - perhaps they will licence it out like they did the PJB MP3 player (great toy I love mine).
I've hired a lot of engineers in my time and I don't think age matters as much as passion and cluefullness.
:-)
I've seen kids (less than 20) who get it and people 50+ who get it (didn't have many applicants who were over 50 so it's really hard to tell beyond that). I've also seen people of all ages who were clueless.
A good age mix is often a distinct advantage in a product team as it lets some of the old hands inject some real world wizdom into things. Better products are the result.
John (Retired at 37
I think for most practical purposes the big issue in firewalls is configuration (or lack of) and user stupidity (if users have remote access without hardware authentication then assume the bad guys do too). Add to that an eggshell mentality (hard wall soft middle) and you have a recipie for bad security. If you are a real badguy (as opposed to a script kiddie) social engineering beats software attacks by a wide margin.
In a free country people get to make choice about how much information the do and don't give away - what TRUSTe seeks to do is give them background to make an informed choice. TRUSTe provides a level of confidence that an organization will keeps it's word - nothing else.
I think where people get upset with this is that it's not an "implicit privacy" model in which all info is protected unless explicit concent is given. An implicit privacy model would probably be a good thing however it's a good first step to shine a light on whatever is already there.
John Pettitt
Former CTO Beyond.com & CyberSource (now retired)