Designing Secure Software Blog

Writing about software design is difficult because there is little to no standard methodology or practice – everyone does it differently. So there is a challenge as to how to show secure software design.

Copy edit is the last chance to make significant changes to the text. Most chapters involve plenty of sentence rewriting and a few moves of a paragraph, but much of the delta is punctuation and word choice.

The artwork came back as a PDF with one drawing per page, labeled by filename. The first batch was pretty good, considering that Richard (I learned the artist’s name) must have had no idea what the symbols meant.

This is the obligatory post that accompanies the skeleton first draft of the website. Setting up Hugo at GitLab was easy: fork Hugo from https://gitlab.com/pages/hugo, follow the simple instructions, and start editing files in the content/ directory.

Copy edit phase starts this week with two chapters (Ch 1 and 4). The chapters that resulted from developmental editing have been converted to a new style regime, and are now ODT instead of DOCX format. Each chapter arrives with edits and comments from the copy editor.

Perhaps it was due to poor grades in Art class back in my school days, but I quickly realized that the sketches I did for graphics in the book we not going to be up to par. Having never worked with a pro, I didn’t invest a lot of time as the drawings were not getting better it seemed, and when production began the publisher sent them to a pro to fix up.

The section of the book on SQL injection needs to illustrate how an attack string gets inserted into a text string representing a SQL statement with unexpected results. The standard way of highlighting a part of a string available was to use bold like this: