[Opendnssec-develop] Use Case diagram for OpenDNSSEC

[Rickard Bondesson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> I've taken the liberty of drawing up a Use Case diagram, 
> describing OpenDNSSEC as it interacts with its environment.  
> This can be found on a working page with OpenDNSSEC design documents:

Great initiative! Comes in handy when you would like a summarization of the different use cases and that our software conforms to the intended use. Also a good start when we are doing a security review with tools like misuse cases.

> http://openfortress.nl/tmp/opendnssec/
> 
> Comments and updates are welcome.  The whole idea of making 
> these design documented is to check if we have the same 
> mindset.  If you see anything "funny" you should therefore speak up :)

Is it possible to add a security level to each component of the data flow diagram (DFD)? White/black/grey meaning that the incoming data/resource is trusted/untrusted/somewhat-trusted. Useful when evaluating the source code for any security holes.

The DFD is essentially a more detailed description on the Signer Engine with its surrounding. Any comments by the Signer Engine development team? Does this conform to your mindset?

// Rickard

-----BEGIN PGP SIGNATURE-----
Version: 9.8.3 (Build 4028)
Charset: utf-8

wsBVAwUBSXRN8uCjgaNTdVjaAQikhgf+LBXjucE++D5+sqJ/Jcu87Cm8Gsb37Csg
VCxrDK22t/ClBaUiEusBUwQDKWY9CuqngvuwF9d5DjacZYktJdqUTiL3FcHCJHDW
ejZCo4fmee9djAtz6wOX2L/XnL5XG0jxZDfB0g+HfhvChCnMozSFI7FS+kyKCZRE
YFfUYg5SC3P28USt+lZKZAtaWolTJwtk/aeiKV/tdyzBGZFNzFUlRqyeFDx6NmHx
gU1SO5oikMEjcGZyuAjF+K5IiLSZwgUE/W/FxJIFUBvkVJtyvGZZwd8i4/mCSZ/O
ebTB87tOiQsDqyX53A3sh4+kceP06zzhk24tdnVTP/fq1gaP8+ejeQ==
=V+qD
-----END PGP SIGNATURE-----