2026-02-22 GnuCash IRC logs
01:18:05 *** fell has quit IRC
01:18:54 *** fell has joined #gnucash
01:18:54 *** ChanServ sets mode: +o fell
02:50:07 *** AdrienM__ has quit IRC
04:20:41 *** fred has joined #gnucash
05:10:02 *** juliademille has quit IRC
05:10:58 *** juliademille has joined #gnucash
05:10:58 *** ChanServ sets mode: +v juliademille
07:38:47 *** fred has quit IRC
07:39:17 *** fred has joined #gnucash
08:54:59 *** fred has quit IRC
08:55:07 *** fred has joined #gnucash
08:58:27 *** fred has quit IRC
08:58:35 *** fred has joined #gnucash
08:59:47 *** fred has quit IRC
09:50:17 *** warlord has joined #gnucash
09:50:17 *** gncbot sets mode: +o warlord
10:08:27 <warlord> .
10:36:13 *** AdrienM has joined #gnucash
10:36:13 *** ChanServ sets mode: +v AdrienM
10:51:19 *** fell has quit IRC
10:58:05 *** fell has joined #gnucash
10:58:05 *** ChanServ sets mode: +o fell
12:58:18 *** fell has quit IRC
15:54:58 *** juliademille has quit IRC
15:55:55 *** juliademille has joined #gnucash
15:55:55 *** ChanServ sets mode: +v juliademille
16:54:42 *** fell has joined #gnucash
16:54:42 *** ChanServ sets mode: +o fell
17:05:59 <fell> jralls, warlord: Is there some known reason,why I can't reach www.gnucash.org?
18:33:56 <jralls> fell, www has been down since last Tuesday. You should have gotten Linas's explanation of the problem in gnucash-core yesterday.
18:34:29 <warlord> Even worse, the gnucash.org DNSsec signatures are going to expire on Tuesday, which will take /all/ of Gnucash.org offline.
18:36:49 <jralls> Unless Linas's ISP comes through and fixes the static address problem tomorrow or Linas moves the authoritative domain files somewhere else from his home nameserver.
18:41:33 <warlord> Yeah.
18:42:07 <warlord> Luckily, /one/ of the primary servers is mine, so if he can't get back online it's not a total loss.
18:42:18 <warlord> but it's still going to be a PITA.
18:49:01 <jralls> If one of the primary servers is yours and his is unreachable can't you just update the DNSsec keys and propagate?
18:49:19 <warlord> I don't have the keys, so I cannot sign the domain.
18:49:59 <warlord> He could theoretically re-sign them and email them to me, and I can re-configure my server to serve them.
18:50:44 <jralls> What's theoretical about that? Isn't that you you usually update the keys on your instance?
18:50:53 <jralls> er, how you...
18:54:14 <warlord> No.. He re-signs the zone, publishes it on his primary server, and then my secondary server pulls the updated (signed) data from his server and (re)services it as an authoritative source.
18:54:30 <warlord> er, (re)serves it..
18:58:03 <jralls> Interesting. So normally no manual intervention on your part now that you have the automatic reminder to re-sign. And I guess more secure since the file transfer is over a secure connection thanks to the old DNSsec key.
19:05:16 <warlord> Basically, yeah. The reminder is there to notify us if the automated signing fails (or the transfer to my server fails). It doesn't really differentiate.
19:05:29 <warlord> And the zone is secured because of the DNSsec signatures.
23:10:00 *** jonakeys has quit IRC
23:10:08 *** jonakeys has joined #gnucash