3 ms·

I built an application for low-latency financial application in SBCL using genetic programming. This runs about 75k lines. I have a bunch of small projects tot

by wglb 5y ago

I built an application for low-latency financial application in SBCL using genetic programming. This runs about 75k lines. I have a bunch of small projects totaling about 70k lines. This includes * Simple library to do application logging. Provides time stamp options, file naming options, others. * Pull apart excel spreadsheet to generate exception report. * Download images from Montana roadside cameras (15 minute cycle), Glacier park cameras (5 minute cycle). Includes crude detection of stars for dark images. * Convert rtf format to text to enable reasonable text-bases search. Used in scanning all household documents. * Parse burp logs to prepare for statistical analysis * configurations as s-expressions * Parse, report ham radio logs from trlog, wsjtx others. * Create makefiles for LaTeX projects * Command launcher to simplify working with many emacs projects, starting x-terminals for other systems, monitoring application status, tracking ntp sync of multiple systems. * Very small program to bump version number as part of lisp program builds. * Generate invoice from journal entries produced by https://github.com/wglb/for-hire-tools * Generate full penetration test report in LaTex from findings, glossary entries, vulnerability counts. * Simple api utils package used for web penetration tests * Pinboard api access used to generate pages for https://ciexinc.com/blog/solarwinds-articles/ * Library to read, dissect pcap files. (Unfinished) And countless tiny replacements for shell scripts.

tlavoie 5y ago
Out of curiosity, what sorts of processing were you doing for burp and penetration test data? I'm in security, and reporting on tests is always something of a pain point.
- wglb 5y ago
  So the burp log analyzed certain statistics about cookies and url segments. Nowadays there might be ways to do that within burp. Could also look for secrets in bodies. The report one combines all elements of a pen test report including descriptive articles (e.g., what are CSRF, clickjacking, secure headers, and the like), one page for each vulnerability. These pages would include severity, impact, CVE links and CWE links, whether the vuln is closed, open, or risk accepted. Included is a tally of vulns by severity. A glossary of terms is also included. At the end is the glossary and index. A table of contents of course is at the beginning. One improvement is a pie chary of vulnerabilities. The lisp program generates LaTeX and references the article document type. Vastly simplified generating the report as the test went along. Document was one unit and no paring was required.
  - tlavoie 5y ago
    Very cool, thanks for the info!
    - wglb 5y ago
      Some of these will end up on github, but it will take a little time.
      - tlavoie 5y ago
        Nice. I suspect I'll mostly stick to taking inspiration, rather than code. I am looking for a solution for an eventual replacement for our team's reporting tool, but would be more likely to simply buy something since writing a replacement isn't my expected role. ;)

by wglb 5y ago

tlavoie 5y ago

Out of curiosity, what sorts of processing were you doing for burp and penetration test data? I'm in security, and reporting on tests is always something of a pain point.

wglb 5y ago
So the burp log analyzed certain statistics about cookies and url segments. Nowadays there might be ways to do that within burp. Could also look for secrets in bodies. The report one combines all elements of a pen test report including descriptive articles (e.g., what are CSRF, clickjacking, secure headers, and the like), one page for each vulnerability. These pages would include severity, impact, CVE links and CWE links, whether the vuln is closed, open, or risk accepted. Included is a tally of vulns by severity. A glossary of terms is also included. At the end is the glossary and index. A table of contents of course is at the beginning. One improvement is a pie chary of vulnerabilities. The lisp program generates LaTeX and references the article document type. Vastly simplified generating the report as the test went along. Document was one unit and no paring was required.
- tlavoie 5y ago
  Very cool, thanks for the info!
  - wglb 5y ago
    Some of these will end up on github, but it will take a little time.
    - tlavoie 5y ago
      Nice. I suspect I'll mostly stick to taking inspiration, rather than code. I am looking for a solution for an eventual replacement for our team's reporting tool, but would be more likely to simply buy something since writing a replacement isn't my expected role. ;)