profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/Ajedi32/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Andrew Meyer Ajedi32 Wisconsin, USA

Ajedi32/echovr_api_docs 15

Unofficial documentation for Echo VR's HTTP API

Ajedi32/metalsmith-matters 9

A Metalsmith plugin to read file metadata from YAML frontmatter

Ajedi32/git_aliases 8

A repository of useful aliases for use with git (versions 1.7.10 and up). Pull requests are welcome.

Ajedi32/echovr-api 6

Python bindings for Echo VR's HTTP API.

Ajedi32/metalsmith-metafiles 6

A Metalsmith plugin to read file metadata from separate files (as an alternative to frontmatter)

Ajedi32/echovr-tray-tool 2

A small background application for enhancing your experience with Echo VR

Ajedi32/mocha-let 1

Get RSpec-style memoized values in Mocha

Ajedi32/acme-dns 0

Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.

Ajedi32/atom-hard-wrap 0

:ribbon: Hard wrap lines in atom - enhanced version of core autoflow

Ajedi32/bash_settings 0

A couple files containing useful bash aliases that I like to source in my .bashrc file

pull request commentsegmentio/metalsmith-markdown

Bump lodash from 4.17.15 to 4.17.19

Superseded by #52.

dependabot[bot]

comment created time in a day

delete branch segmentio/metalsmith-markdown

delete branch : dependabot/npm_and_yarn/lodash-4.17.19

delete time in a day

PR closed segmentio/metalsmith-markdown

Bump lodash from 4.17.15 to 4.17.19 dependencies

Bumps lodash from 4.17.15 to 4.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lodash/lodash/releases">lodash's releases</a>.</em></p> <blockquote> <h2>4.17.16</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li><a href="https://github.com/lodash/lodash/commit/1144918f3578a84fcc4986da9b806e63a6175cbb"><code>1144918</code></a> Rebuild lodash and docs</li> <li><a href="https://github.com/lodash/lodash/commit/3a3b0fd339c2109563f7e8167dc95265ed82ef3e"><code>3a3b0fd</code></a> Bump to v4.17.16</li> <li><a href="https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12"><code>c84fe82</code></a> fix(zipObjectDeep): prototype pollution (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4759">#4759</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/e7b28ea6cb17b4ca021e7c9d66218c8c89782f32"><code>e7b28ea</code></a> Sanitize sourceURL so it cannot affect evaled code (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4518">#4518</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/0cec225778d4ac26c2bac95031ecc92a94f08bbb"><code>0cec225</code></a> Fix lodash.isEqual for circular references (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4320">#4320</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4515">#4515</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/94c3a8133cb4fcdb50db72b4fd14dd884b195cd5"><code>94c3a81</code></a> Document matches* shorthands for over* methods (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4510">#4510</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4514">#4514</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.19">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mathias">mathias</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

1 comment

1 changed file

dependabot[bot]

pr closed time in a day

PR opened segmentio/metalsmith-markdown

Bump lodash from 4.17.15 to 4.17.21

Bumps lodash from 4.17.15 to 4.17.21. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/f299b52f39486275a9e6483b60a410e06520c538"><code>f299b52</code></a> Bump to v4.17.21</li> <li><a href="https://github.com/lodash/lodash/commit/c4847ebe7d14540bb28a8b932a9ce1b9ecbfee1a"><code>c4847eb</code></a> Improve performance of <code>toNumber</code>, <code>trim</code> and <code>trimEnd</code> on large input strings</li> <li><a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c"><code>3469357</code></a> Prevent command injection through <code>_.template</code>'s <code>variable</code> option</li> <li><a href="https://github.com/lodash/lodash/commit/ded9bc66583ed0b4e3b7dc906206d40757b4a90a"><code>ded9bc6</code></a> Bump to v4.17.20.</li> <li><a href="https://github.com/lodash/lodash/commit/63150ef7645ac07961b63a86490f419f356429aa"><code>63150ef</code></a> Documentation fixes.</li> <li><a href="https://github.com/lodash/lodash/commit/00f0f62a979d2f5fa0287c06eae70cf9a62d8794"><code>00f0f62</code></a> test.js: Remove trailing comma.</li> <li><a href="https://github.com/lodash/lodash/commit/846e434c7a5b5692c55ebf5715ed677b70a32389"><code>846e434</code></a> Temporarily use a custom fork of <code>lodash-cli</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/5d046f39cbd27f573914768e3b36eeefcc4f1229"><code>5d046f3</code></a> Re-enable Travis tests on <code>4.17</code> branch.</li> <li><a href="https://github.com/lodash/lodash/commit/aa816b36d402a1ad9385142ce7188f17dae514fd"><code>aa816b3</code></a> Remove <code>/npm-package</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.21">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~bnjmnt4n">bnjmnt4n</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

0 comment

1 changed file

pr created time in a day

issue openedjoohoi/acme-dns

HA Configuration

Has anyone run acme-dns in a highly available config using the postgres DB? Before I go testing myself, I was just wondering if anyone had multiple instances of acme-dns running against the same PG db without issues?

created time in 3 days

issue commentjoohoi/acme-dns

Allow more than two records?

For those who feel they need multi value TXT records, is the motivation for stuffing TXT records primarily to avoid multiple acme-dns registrations or it avoidance of registrations due to migration? Anything else?

A couple of techniques you can use:

  • host your acme-dns database in a separate/cloud instance so that the registration data survives any migration

  • CNAME your _acme-dns records to an intermediate zone that supports a scripting API. e.g. Google Cloud DNS, Route53 etc, pointing to your final acme-dns TXT records, that way you can always update the intermediate zone without affecting your original _acme-challenge CNAMES (some of which may be in customer domains or ones that are more difficult to update).

If the issue is more around the annoyance/frequency of the initial registration per domain, you could adapt your acme-dns client to auto create the initial CNAME in your domains using a script. This is for larger scale deployments that can afford the time to develop automations. Obviously if you can already script DNS updates you could just skip acme-dns but that still offers a least-privilege/least-responsibility approach for frequent TXT record updates. acme-dns is simple enough in terms of API that you can also build a custom implementation fairly quickly (i.e. one developer for 1-2 weeks) to support your specific use case. Again, this starts to make sense if you are scaling a larger system. I built a custom implementation last week using cloudflare workers and google DNS for an intermediate CNAME zone that in turn can point to the TXT records (hosted in any zone or service).

burdakovd

comment created time in 12 days

issue commentjoohoi/acme-dns

Allow more than two records?

I would still argue that the correct behavior would be to keep the limit and to use unique acme-dns credential set for every unique (sub)domain in the SAN list. The client implementation should support this.

The main point is to make it hard for users to end up with an insecure (or suboptimal) setup. Another point is to avoid ending up in really hard to debug situations where for example the DNS provider or service is unable to serve a large amount of TXT records for a single request.

I think Let's Encrypt supports up to 100 domain names in SAN for a single certificate and the server would need to respond with all of those 100 TXT records for 100 times. The UDP DNS responses have size limits after which the packets get fragmented and I would assume this would have to be remedied by an arbitruary limit again.

The limit is in place to keep it simple in a big scale.

burdakovd

comment created time in 12 days

issue commentjoohoi/acme-dns

Allow more than two records?

If anyone is interested, I made a config option for this - https://github.com/krigga/acme-dns/tree/config-txt-number Please note however that the code I added was never run by me, so use it at your own risk.

burdakovd

comment created time in 12 days

issue commentjoohoi/acme-dns

Allow more than two records?

So, why not just add a settings to the config? Sometimes it would be very helpful, because we have domains like ".sub.domian.tld", ".domain.tld", "domain.tld".

burdakovd

comment created time in 14 days

issue commentjoohoi/acme-dns

Allow more than two records?

While the implementation might well be cursed, the feature is intentional.

It is there to ensure the first priority and design goal of this project: security and limiting the impact of a box getting compromised.

burdakovd

comment created time in 14 days

issue commentjoohoi/acme-dns

Allow more than two records?

This is so cursed IMHO:

https://github.com/joohoi/acme-dns/blob/68bb6ab654b6fb1fe375e08807688c55621513a2/db.go#L168-L169

https://github.com/joohoi/acme-dns/blob/68bb6ab654b6fb1fe375e08807688c55621513a2/db.go#L256

Consider at least use config variable for this, instead of hardcoded limits.

burdakovd

comment created time in 14 days

issue commentjoohoi/acme-dns

Custom DNS record wildcard support

Looks good! This is exactly what I was asking for. Wild cards are always for one domain level. That's the same for certificates. Sounds like it needs documented test cases to get accepted.

Daniel-Nashed

comment created time in 18 days

issue commentjoohoi/acme-dns

Custom DNS record wildcard support

Maybe this PR? https://github.com/joohoi/acme-dns/pull/174

Looks like it needs more tests to get accepted.

Daniel-Nashed

comment created time in 18 days

issue commentjoohoi/acme-dns

Custom DNS record wildcard support

Thanks for the quick answer. that means I didn't do anything wrong.. I understand the main purpose and it works like a charm!

Wildcard DNS entries would serve the same purpose the current A records have. In some lab environments you don't want to install a separate DNS server. But for testing it is often helpful to resolve everything that has no own DNS record to a default host.

When you have two DNS servers in place just for that, this makes the environment more complex. I really like that you can just add DNS entries almost like in a host file without defining your own DNS zone.

For what I need right now I can use CoreDNS in a container. Still having wildcards, would let me use ACME-DNS only in this use case.

Daniel-Nashed

comment created time in 18 days

issue commentjoohoi/acme-dns

Custom DNS record wildcard support

The primary purpose of acme-dns is to serve TXT records to satisfy acme certificate DNS validation. The limited DNS features it has are only there so that it can serve these TXT records and act as a basic (self-hosted) delegated nameserver for an authentication-specific subdomain.

What would be the benefit of providing this wildcard support within acme-dns?

Daniel-Nashed

comment created time in 18 days

issue openedjoohoi/acme-dns

Custom DNS record wildcard support

"Custom DNS records" are very useful specially for small test environments to be used instead of a larger DNS server.

It looks like an A record cannot be a wild-card entry? Or is there any trick?

example:

*.mydomain.com. IN A 1.2.3.4

If` this isn't possible today, could this be added in future? :-)

created time in 18 days

issue commentsegmentio/metalsmith

Long term goals

Pretty good. It seems like the most likely route will be one of the current maintainers taking over the metalsmith IP. Currently we're awaiting the draft of some legal documents to arrange that, and then after that it should hopefully be possible for us to move along with the reorganisation.

ismay

comment created time in 22 days

issue commentsegmentio/metalsmith

Long term goals

How did the meeting go?

ismay

comment created time in 22 days

push eventReddit-Enhancement-Suite/Reddit-Enhancement-Suite.github.io

Ben McGarry

commit sha 1bc2081d32a59d4aaaf2550aa6c5e1cd996e0a77

Update contribute.html

view details

push time in 22 days

push eventReddit-Enhancement-Suite/Reddit-Enhancement-Suite.github.io

Steve Sobel

commit sha 382fd8c3015df441d44517233b341015edb5b545

Update contribute.html

view details

push time in 22 days

push eventReddit-Enhancement-Suite/Reddit-Enhancement-Suite.github.io

Reddit-Enhancement-Suite-Bot

commit sha dccada0db62c3ec08dc7dd1a3667c98ed17519d8

update versions

view details

push time in 23 days

created repositoryefritz/gostgres

created time in 23 days

push eventReddit-Enhancement-Suite/Reddit-Enhancement-Suite.github.io

Reddit-Enhancement-Suite-Bot

commit sha b69a042216a487f0fcc6681eb439fb387fc5de6e

changelog v5.22.4

view details

push time in 23 days

startedrampxxxx/frr-syntax

started time in 24 days

startedRF5/danbooru-pretrained

started time in 25 days

startedDualCoder/vgpu_unlock

started time in a month

created repositoryqlyoung/clabs

my personal containerlab topologies

created time in a month

delete branch WebAssembly/proposals

delete branch : dtig-fix-indentation

delete time in a month