- Project tools
-
-
- How do I...
-
| Category |
Featured projects |
| scm |
Subversion,
Subclipse,
TortoiseSVN,
RapidSVN
|
| issuetrack |
Scarab |
| requirements |
xmlbasedsrs |
| design |
ArgoUML |
| techcomm |
SubEtha,
eyebrowse,
midgard,
cowiki |
| construction |
antelope,
scons,
frameworx,
build-interceptor,
propel,
phing
|
| testing |
maxq,
aut
|
| deployment |
current |
| process |
ReadySET |
| libraries |
GEF,
Axion,
Style,
SSTree
|
| Over 500 more tools... |
|
Security.c#
As you may recall, the Sumerians had a lot of trouble with the
security of the pyramids. Most of the tombs were robbed of their
riches shortly after they were completed.
What they failed to do was work through all their use cases and
review their designs with a security checklist in mind. A step
further would have been to work through a fault-tree analysis for
every possible security failure.
Sometimes in modern open source, we expect to identify security
problems and defects by having "many eyes" look at the code. The
Sumerian code reminds us that any kind of code review can be hard
if the code does not follow the style guidelines that we are
familar with.
What if our positions were reversed? Just imagine how confused
the Sumarins would be if they had to read our Hungarian notation.
|
|
|
prev | next
|