3 ms·
I won't argue with you the difference between a technical document and a document with technical details. You're welcome to that definitional win. There are in
by loteck 10y ago
I won't argue with you the difference between a technical document and a document with technical details. You're welcome to that definitional win.
There are interesting technical details in this document about the exact methods, vectors, files, timelines, etc used in both offense and defense of this incident. They would be of interest and value to many in this community regardless of the partisan agenda of the committee.
- tptacek 10y agoIt is not my argument that this is an uninteresting or uninformative document.
- superuser2 10y agoA technical document about a breach would explain the mechanisms for the vulnerabilities and exploits involved, and discuss how systems could be architected and written differently to avoid them. This document walks up the abstraction chain several notches and attacks the org chart and security policy of the MS Word variety, not the way things were written or configured (except insofar as bad config stemmed from not enough teams of paper not enforced well enough). It is pitched at the kind of CIO/CTO who could just as easily be any other CxO, not at engineers.