Package: python-certbot-dns-rfc2136-doc
Source: python-certbot-dns-rfc2136
Version: 4.0.0-1+dc1
Architecture: all
Maintainer: Debian Let's Encrypt <team+letsencrypt@tracker.debian.org>
Installed-Size: 122
Depends: libjs-jquery (>= 3.6.0), libjs-sphinxdoc (>= 8.1), sphinx-rtd-theme-common (>= 3.0.2+dfsg)
Homepage: https://certbot.eff.org/
Priority: optional
Section: dc-net
Filename: pool/dc-net/p/python-certbot-dns-rfc2136/python-certbot-dns-rfc2136-doc_4.0.0-1+dc1_all.deb
Size: 19040
SHA256: a41f20d2084a04e662a81a756bb0096f4dd23f0636a610e06f4e5c959c58685a
SHA1: a9fad505f974a6df7d8fa31fa72e04fd3f033010
MD5sum: 654b23cb366795727fd5c6964ec7a36d
Description: Documentation for the RFC 2136 DNS plugin for Certbot
 The objective of Certbot, Let's Encrypt, and the ACME (Automated
 Certificate Management Environment) protocol is to make it possible
 to set up an HTTPS server and have it automatically obtain a
 browser-trusted certificate, without any human intervention. This is
 accomplished by running a certificate management agent on the web
 server.
 .
 This package contains the documentation for the RFC 2136 DNS plugin to
 the main application.

Package: python3-certbot-dns-rfc2136
Source: python-certbot-dns-rfc2136
Version: 4.0.0-1+dc1
Architecture: all
Maintainer: Debian Let's Encrypt <team+letsencrypt@tracker.debian.org>
Installed-Size: 58
Depends: certbot, python3-certbot-abi-4 (>= 4.0), python3-acme, python3-certbot, python3-dnspython, python3:any
Enhances: certbot
Homepage: https://certbot.eff.org/
Priority: optional
Section: dc-net
Filename: pool/dc-net/p/python-certbot-dns-rfc2136/python3-certbot-dns-rfc2136_4.0.0-1+dc1_all.deb
Size: 11308
SHA256: 1b5b7c7004d153ac1c40724b4f1c9b7e5ae1502d5198ae0843da63efab1dbfa2
SHA1: 2ac09ba96aee6f6772e76ab8189a84a9e7724f13
MD5sum: 83469dba97c403648a5c57b8737b0e40
Description: RFC 2136 DNS plugin for Certbot
 The objective of Certbot, Let's Encrypt, and the ACME (Automated
 Certificate Management Environment) protocol is to make it possible
 to set up an HTTPS server and have it automatically obtain a
 browser-trusted certificate, without any human intervention. This is
 accomplished by running a certificate management agent on the web
 server.
 .
 This agent is used to:
 .
   - Automatically prove to the Let's Encrypt CA that you control the website
   - Obtain a browser-trusted certificate and set it up on your web server
   - Keep track of when your certificate is going to expire, and renew it
   - Help you revoke the certificate if that ever becomes necessary.
 .
 This package contains the RFC 2136 DNS plugin to the main application.

Package: spoolinger
Version: 0.3.2-1
Architecture: all
Maintainer: Marc Dequènes (Duck) <Duck@DuckCorp.org>
Installed-Size: 82
Depends: ruby:any, ruby, ruby-log4r (>= 1.1.10), ruby-daemons (>= 1.1.9), ruby-eventmachine (>= 1.0.7), ruby-activesupport (>= 2:5.2.2.1), ruby-rb-inotify (>= 0.9.10), kwalify (>= 0.7.2)
Homepage: https://projects.duckcorp.org/projects/spoolinger/wiki
Priority: optional
Section: dc-net
Filename: pool/dc-net/s/spoolinger/spoolinger_0.3.2-1_all.deb
Size: 14400
SHA256: 348540705cf98c32a8c2fcaf141b9b323fb61f0752d5bf0fc419b77c8a49f59e
SHA1: bfecc1f0fd557d4671c91784801114b84d1aaec2
MD5sum: fa9732cf98c84906f8fa6e58bf266e89
Description: generic spool manager
 The Spoolinger is a generic spool manager, watching for incoming files
 in a specific directory and scheduling their processing.
 .
 Features:
   - scheduling based on concurrency and min/max age
   - gathering of file data using file name and content regex to be
     used in pattern replacement
   - cancel mode (with pattern replacement)
   - running of an external processing command (with pattern
     replacement)
   - "load check" via external command or Ruby plugin to allow
     processing depending on external conditions
   - logging with ajustable verbosity to help debug problems