Re: Announcement: LetsDNS release 1.0 is now available

2022-04-13 Thread Matthias Fechner
Am 13.04.22 um 10:26 schrieb Damian: https://mail.sys4.de/mailman/listinfo/dane-users does not work? thanks, that information was missing. Gruß, Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-13 Thread Jürgen Echter
Am Mittwoch, April 13, 2022 10:22 CEST, schrieb Matthias Fechner : > Am 12.04.2022 um 19:15 schrieb Ralph Seichter: > > I'm happy to usedane-us...@sys4.de if you don't mind it. I consider > > that one pretty much*your* mailing list and did not mean to just barge > > in, although I had

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-13 Thread Damian
how can I sub-scr1be to this list? Sorry to write it this way, but there is a stupid filter in place that blocks the email. https://mail.sys4.de/mailman/listinfo/dane-users does not work?

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-13 Thread Matthias Fechner
Am 12.04.2022 um 19:15 schrieb Ralph Seichter: I'm happy to usedane-us...@sys4.de if you don't mind it. I consider that one pretty much*your* mailing list and did not mean to just barge in, although I had obviously hoped for your input in particular. how can I sub-scr1be to this list? Sorry

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Ralph Seichter
* Viktor Dukhovni: > Perhaps dane-users then. I don't find Github to be a good forum for > discussing design options. I'm happy to use dane-us...@sys4.de if you don't mind it. I consider that one pretty much *your* mailing list and did not mean to just barge in, although I had obviously hoped

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Viktor Dukhovni
> On 12 Apr 2022, at 1:05 pm, Ralph Seichter wrote: > > I invite you and other interested parties to discuss this on GitHub [1] > rather than the Postfix mailing list. Release 1.0 is meant to provide > core functionality, and follows the "release erly and often" approach. > There is of course

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Ralph Seichter
* Erwan David: > as you can see, let'sDNS would have to act in cooperation with the > certificate update. Which is exactly why I launch LetsDNS from a "dehydrated" hook whenever the latter has obtained a new certificate, but before that certificate is moved from staging into production. This

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Ralph Seichter
* Viktor Dukhovni: > My first impression reading the docs is that "letdns" is not involved > in certificate rollovers. Its job is solely to automate TLSA record > updates. Indeed. > Are TLSA records matching the previous cert/key retained? No, LetsDNS is stateless beyond the configuration

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Erwan David
Le 12/04/2022 à 18:52, Ralph Seichter a écrit : * Erwan David: Does it handle restarting/reloading a program when changing the certificate ? Postfix does not need it, but dovecot does. LetsDNS does not obtain or change TLS certificates, because that's what specialised ACME clients like

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Ralph Seichter
* Erwan David: > Does it handle restarting/reloading a program when changing the > certificate ? Postfix does not need it, but dovecot does. LetsDNS does not obtain or change TLS certificates, because that's what specialised ACME clients like "dehydrated" or "certbot" are for. A hook function in

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Viktor Dukhovni
> On 12 Apr 2022, at 12:36 pm, Erwan David wrote: > > Does it handle restarting/reloading a program when changing the certificate ? > Postfix does not need it, but dovecot does. My first impression reading the docs is that "letdns" is not involved in certificate rollovers. Its job is solely

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Erwan David
Le 12/04/2022 à 15:30, Ralph Seichter a écrit : I'm happy to announce that LetsDNS release 1.0 is now available and ready for public use. Website: https://letsdns.org GitHub : https://github.com/LetsDNS/letsdns PyPI : https://pypi.org/project/letsdns/ LetsDNS is a utility to manage

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Ralph Seichter
* Ruben Safir: > automated systems with root access are inherently not secure Ah, nothing quite like shooting sweeping statements from the hip, is there? :-) See paragraph one of https://letsdns.org/operation.html . -Ralph

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Patrick Proniewski
Hello, This statement is at best off topic. Worst case scenario, it's toxic. And you can be polite, too. Thank you. > On 12 Apr 2022, at 16:58, Ruben Safir wrote: > > automated systems with root access are inherently not secure > > > On Tue, Apr 12, 2022 at 03:30:57PM +0200, Ralph Seichter

Re: Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Ruben Safir
automated systems with root access are inherently not secure On Tue, Apr 12, 2022 at 03:30:57PM +0200, Ralph Seichter wrote: > I'm happy to announce that LetsDNS release 1.0 is now available and > ready for public use. > > Website: https://letsdns.org > GitHub :

Announcement: LetsDNS release 1.0 is now available

2022-04-12 Thread Ralph Seichter
I'm happy to announce that LetsDNS release 1.0 is now available and ready for public use. Website: https://letsdns.org GitHub : https://github.com/LetsDNS/letsdns PyPI : https://pypi.org/project/letsdns/ LetsDNS is a utility to manage DANE TLSA records in DNS servers with only a few