so has someone analyzed how much "lost productivity" that crap has cost us? especially for the droves of bubbas and skeeters that call in sick from drinking too many cases watching the game???
Agree that we need OPEN standards and good interop to make this work. As others have said, part of the difficulty isn't that the software doesn't exist, but more that it is not transparent to end users. That's the tough nut to crack, but it has been done before in other areas. SSL is not a simple protocol, but most browsers do HTTPS pretty smoothly now and keep users from totally freaking out.
As for key storage, multiple repositories are the most likely answer. An to make it easy to get the keys from a myriad of repositories, just look at the "trusted authorities" already embedded in your browser. Yes, I know that x.509 and PGP are different things, but my point is the same. Integrate the well-known (and hopefully trusted) repositories into the client software. As long as you give the user the ability to add/remove them, it would be a good start.
Right on! As a former military guy I remember the misery of working on "DII/COE compliant" systems. What a horrible waste. The DII/COE "enhancements" took my nice little sun workstations and brought them to their knees. All this while providing virtually zero added benefit. My office was able to assemble a far superior system just by putting all the applications we needed on some good workstations (not NT!). Like you, everytime DII/COE was mentioned in the office or at exercises everyone just laughed or blurted out some nasty comment. We need to stop letting high-ranking officers and civilians who have no clue about systems dictate our selections.
The US gov't: Aspiring to mediocrity and failing to achieve it!
Slashdot Mirror
So should we go ahead and slap on a bumper sticker that reads:
"WU-FTPD, providing remote spacecraft root since 200x"
so has someone analyzed how much "lost productivity" that crap has cost us? especially for the droves of bubbas and skeeters that call in sick from drinking too many cases watching the game???
*hiccup*
;)
Agree that we need OPEN standards and good interop to make this work. As others have said, part of the difficulty isn't that the software doesn't exist, but more that it is not transparent to end users. That's the tough nut to crack, but it has been done before in other areas. SSL is not a simple protocol, but most browsers do HTTPS pretty smoothly now and keep users from totally freaking out.
As for key storage, multiple repositories are the most likely answer. An to make it easy to get the keys from a myriad of repositories, just look at the "trusted authorities" already embedded in your browser. Yes, I know that x.509 and PGP are different things, but my point is the same. Integrate the well-known (and hopefully trusted) repositories into the client software. As long as you give the user the ability to add/remove them, it would be a good start.
Right on! As a former military guy I remember the misery of working on "DII/COE compliant" systems. What a horrible waste. The DII/COE "enhancements" took my nice little sun workstations and brought them to their knees. All this while providing virtually zero added benefit. My office was able to assemble a far superior system just by putting all the applications we needed on some good workstations (not NT!). Like you, everytime DII/COE was mentioned in the office or at exercises everyone just laughed or blurted out some nasty comment. We need to stop letting high-ranking officers and civilians who have no clue about systems dictate our selections.
The US gov't: Aspiring to mediocrity and failing to achieve it!