···55 "os"
66 "text/template"
77 "time"
88+99+ "github.com/go-faker/faker/v4"
810)
9111012var (
···2527 panic(err)
2628 }
2729 defer fout.Close()
3030+3131+ name := faker.Name()
28322933 data := map[string]string{
3034 "Date": *date,
···3337 "Project": *project,
3438 "ProjectLink": *projectLink,
3539 "Summary": *summary,
4040+ "Name": name,
3641 }
37423843 tmpl := template.Must(template.New("article").Parse(articleTemplate))
···5560In the hours following the release of [{{.CVE}}]({{.CVELink}}) for the project [{{.Project}}]({{.ProjectLink}}), site reliability workers
5661and systems administrators scrambled to desperately rebuild and patch all their systems to fix {{.Summary}}. This is due to the affected components being
5762written in C, the only programming language where these vulnerabilities regularly happen. "This was a terrible tragedy, but sometimes
5858-these things just happen and there's nothing anyone can do to stop them," said programmer Willodean Santorella, echoing statements
6363+these things just happen and there's nothing anyone can do to stop them," said programmer {{.Name}}, echoing statements
5964expressed by hundreds of thousands of programmers who use the only language where 90% of the world's memory safety vulnerabilities have
6065occurred in the last 50 years, and whose projects are 20 times more likely to have security vulnerabilities. "It's a shame, but what can
6166we do? There really isn't anything we can do to prevent memory safety vulnerabilities from happening if the programmer doesn't want to