Re: ra_serf not storing client cert creds

2018-07-25 Thread Daniel Shahaf
Philip Martin wrote on Wed, 25 Jul 2018 15:08 +0100: > I've noticed a feature that seems to be have been lost when we switched > from neon to serf: serf doesn't store the client cert creds. There are > two bits of data, the path to the pkcs12 file and the password for the > private key. The

ra_serf not storing client cert creds

2018-07-25 Thread Philip Martin
I've noticed a feature that seems to be have been lost when we switched from neon to serf: serf doesn't store the client cert creds. There are two bits of data, the path to the pkcs12 file and the password for the private key. The ra_serf library will prompt for these, if

Re: authz changes between 1.9 and 1.10

2018-07-25 Thread Branko Čibej
On 25.07.2018 08:21, Daniel Shahaf wrote: > Philip Martin wrote on Tue, 24 Jul 2018 23:37 +0100: >> Branko Čibej writes: >>> It describes designed behaviour. If we change it, we should do it >>> carefully, as I wrote above. Also I think it turns out that the authz >>> section in the release notes

Re: authz changes between 1.9 and 1.10

2018-07-25 Thread Branko Čibej
On 25.07.2018 00:37, Philip Martin wrote: > Branko Čibej writes: > >> On 20.07.2018 14:59, Philip Martin wrote: >>> In 1.9 it was possible to repeat, or reopen, a section: >> It's an intentional change that is documented in the design wiki page. > And only there, it didn't make the release notes.

Re: authz changes between 1.9 and 1.10

2018-07-25 Thread Daniel Shahaf
Philip Martin wrote on Tue, 24 Jul 2018 23:37 +0100: > Branko Čibej writes: > > It describes designed behaviour. If we change it, we should do it > > carefully, as I wrote above. Also I think it turns out that the authz > > section in the release notes misses a behaviour change or two. It should