Thursday, 17 December 2020

Dear Santa Pune,

I have been a good boy this year.

For Christmas 2021, I would like:

  • Custom Properties on all entities (including ability to filter via the REST API) so that System Integration is actually possible.
  • V3 of the REST API published, and under SEMVER
  • The broken Alerting API to be fixed (see various other FEED tickets)
  • The UI to finally be self-consistent (either back with the old style or with the new style - I really don't care)
  • To receive a reference number when I send a support/feedback ticket and to be able to track its progress via the UI
  • Themes / Dark Mode
  • A machine-readable Audit Log for ALL Create/Update/Delete actions with a published, consistent JSON schema

I hope you are able to deliver all the releases to the good boys and girls.

Happy Christmas,

David

p.s. Also:

  • A last_updated field on all entities

Wednesday, 9 December 2020

Getting Remote Explorer to work in VS Code

 Follow the instructions in this post:

https://github.com/PowerShell/Win32-OpenSSH/issues/1263#issuecomment-699148072

Friday, 6 November 2020

LogicMonitor LMGlobalData

 To view additional information about your LogicMonitor account, press F12 in Chrome, go to the Console and type:

LMGlobalData

Tuesday, 22 September 2020

Timing cURL

This article ALMOST provides the information needed to add timing output to your cURL query:

Unfortunately, it gets the file format wrong.

Instead, the file should contain the following:

time_namelookup: %{time_namelookup}\n time_connect: %{time_connect}\n time_appconnect: %{time_appconnect}\n time_pretransfer: %{time_pretransfer}\n time_redirect: %{time_redirect}\n time_starttransfer: %{time_starttransfer}\n ———\n time_total: %{time_total}\n
curl -w "@curl-format.txt" -o /dev/null -s http://wordpress.com/

What this does:

  • -w "@curl-format.txt" tells cURL to use our format file
  • -o /dev/null redirects the output of the request to /dev/null
  • -s tells cURL not to show a progress meter
  • http://wordpress.com/ is the URL we are requesting

Tuesday, 23 June 2020

Lets Encrypt certificates for devices on private networks

Here's the process for creating a Let's Encrypt C.509 certificate for devices on private networks:

You will need:
  • Access to your DNS server to create TXT DNS records
  • Windows machine
  • PuttyGen installed
  • choco installed
  • win-acme installed with:
    • choco -y install win-acme
  • openssh installed with:
    • choco -y install openssh
  1. Create two identical files called create.bat and delete.bat with the following contents:
    • echo %1 %2 %3
  2. Create another file called sign.bat with the following contents:
    1. wacs --target csr --csrfile .\csr.txt --pkfile .\rsa4096.private.key --validationmode dns-01 --validation script --dnscreatescript .\create.bat --dnsdeletescript .\delete.bat --store pemfiles --pemfilespath .
  3. Generate an RSA 4096 Private key using PuTTYGen or OpenSSH called rsa4096.private.key
  4. Run the batch file
  5. While the ACME script is retrying, manually create the TXT DNS record for _acme-<DOMAIN NAME> with the value provided in the script output/
  6. If needs be, while the script is retrying, flush the DNS cache with:
    • ipconfig /flushdns
  7. Delete the TXT record when done
  8. The PEM file ending .crt.pem contains your X.509 certificate.