https://www.zaita.com

You can see the product overview: https://www.zaita.com It's architecture and usage is nicely documented: https://docs.zaita.com

Unfortunately, you do need to sign up to have a play, but there is a demo instance that doesn't require a credit card. Just enter an email (I won't send you any emails) and password.

Keen for feedback. I've found the major players in the industry are only interested in Enterprise arrangements. I wanted something I could use in my home lab across my many docker containers etc, but still had cool features like network discovery and certificate transparency log scanning.

Comments URL: https://news.ycombinator.com/item?id=48231769

Points: 10

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=43958277

Points: 3

# Comments: 0

Given that all auto-differentiation is an approximation anyways. I've found existing tooling (CppAD, ADMB, ADOL-C, Template Model Builder (TMB)) work fine. You don't need to come up with a differentiable problem or re-parameterize. Why would I pick this over any of those?

This works so well, we actually package a library with our binary that contains the unit tests so the end user can run them locally without having to download/build anything. This has been super useful in identifying calculation differences between Linux/Windows/MacOS and processors. When a user reports an issue, we can ask them to run the unit tests just by running (./binary --test) and then give us the results.

For multiple servers running the same domain, you can configure them all the same and they will get certificates fine. If required, they will get a new certificate from LE; if this is not required then LE will provide the current certificate to the server. There maybe a short time where the actual certificate on two servers maybe different, but both would still be considered valid. So there really shouldn't be any plumbing required. (edit: This is dependent on you having a sensible way to load balance them. If you're just running IP round-robin then it's going to be difficult, but that is what scp and custom routes are for).

I use LE for multiple domains, on multiple systems. Internal and external with no issue. I've even had certificates revoked by LE and it's never had any operational impact.

As you move through from code to production we have multiple stage gates and steps.

- From a code perspective, we use dependency and code scanning (yarn audit, sonarcloud, sonarcube etc). Sonarcloud has nice IDE integrations.

- Code is pushed and is picked up by a pipeline, further scans are done looking for vulnerabilities/CVEs etc. If any significant ones are found, the pipeline fails (yarn audit, sonarcloud, sonarcube, Palo Alto container scanner, docker bench etc)

- The pipeline deploys to test and does automated checking

- Prior to a production deployment, the pipeline must be manually approved.

- Once in production, we use further scanning and monitoring (Security Hub/Centre, Tenable, SIEM)

Our developers have no direct ability to change the production systems in any way. But, they can write code and commit to our Git repository as much as they want. Everything from that point is automated (except for manual approvals).

Comments URL: https://news.ycombinator.com/item?id=27375401

Points: 64

# Comments: 49

Comments URL: https://news.ycombinator.com/item?id=26484160

Points: 5

# Comments: 4

Comments URL: https://news.ycombinator.com/item?id=26231083

Points: 1

# Comments: 0

TBH I accredit dumb luck more than anything to finding the cause of this. It took many hours.

This code was specifically C++ because we had the intention of integrating with libraries like CppAD and ADOL-C.

And yea you're right on the associative mistake. Will correct this :)

I didn't want to go too far into the background of floating point math in the post as it wasn't ultimately the issue, just something I was mindful of.