| { config, pkgs, ... }: | |
| let | |
| stdenv = pkgs.stdenv; | |
| URIEncode = pkgs.perlPackages.buildPerlPackage { | |
| pname = "URI-Encode"; | |
| version = "1.1.1"; | |
| src = pkgs.fetchurl { | |
| url = "mirror://cpan/authors/id/M/MI/MITHUN/URI-Encode-v1.1.1.tar.gz"; | |
| sha256 = "0fr410f2hiscm9dv85fwr2hyz1jjb445ady2z6617h0nf17cxfab"; |
| ldkeylog.so: ldkeylog.c | |
| gcc -Wall -shared -fPIC -O3 "$<" -o "$@" |
| #!/usr/bin/env python3 | |
| import sys, struct, io | |
| def read_hdr(f): | |
| d = f.read(12*4) | |
| dMagic = d[0:4] | |
| magic, version, size, entrySize, entryCount, blockSize, blockCount, resv0, resv1, resv2, resv3, checksum = struct.unpack('>' + 'I'*12, d) | |
| print(''' | |
| PNOR Header | |
| Magic: {magic:#010x} ({dMagic}) |
This is a rough sketch I've put together in my mind of how an 'ACME daemon' might end up looking.
acmetool is designed for batch operation which works well for small use cases but large scale deployments will work better with a daemon. This will probably expose a service via an HTTP API, so that arbitrary parts of a service provider's stack can request certificates.
This API will need to be asynchronous as it may take arbitrarily long for 'acmed'
| // Reads DNS records in zone file format on stdin and outputs them in generic | |
| // RFC3597 format. This is useful if you need to configure DNS records for a | |
| // nameserver which doesn't support the rrtypes you're trying to configure. | |
| // | |
| // Supports whatever rrtypes that github.com/miekg/dns supports, which tends to | |
| // be pretty exhaustive. | |
| package main | |
| import ( | |
| "fmt" |