On 21 Jul 2014, at 21:42, Lukas Slebodnik lsleb...@redhat.com wrote:
On (21/07/14 14:08), Jakub Hrozek wrote:
On Mon, Jul 21, 2014 at 01:55:20PM +0200, Jan Cholasta wrote:
On 18.7.2014 06:41, William wrote:
Ignore that last patch, I messed up and didn't include a .h file. Here
On Mon, 2014-07-21 at 17:15 +0200, Jakub Hrozek wrote:
On Mon, Jul 21, 2014 at 11:35:31PM +0930, William wrote:
On 21 Jul 2014, at 21:42, Lukas Slebodnik lsleb...@redhat.com wrote:
On (21/07/14 14:08), Jakub Hrozek wrote:
On Mon, Jul 21, 2014 at 01:55:20PM +0200, Jan Cholasta
into the xml file, removed the
references to the .pot file.
--
William will...@firstyear.id.au
From 13c1915264bb77c0d780453de978a5eff411d656 Mon Sep 17 00:00:00 2001
From: William B will...@adelaide.edu.au
Date: Wed, 16 Jul 2014 11:45:02 +0930
Subject: [PATCH] Allow sss_cache tool to flush known
the case.
From 29cdcbd9a20cfbd72c5a8d103f58e3f153887d73 Mon Sep 17 00:00:00 2001
From: William B will...@adelaide.edu.au
Date: Wed, 16 Jul 2014 11:45:02 +0930
Subject: [PATCH] Allow sss_cache tool to flush known hosts cache
---
src/confdb/confdb.h| 2 ++
src/config/etc
On Tue, 2014-07-15 at 15:57 +0200, Jan Cholasta wrote:
On 11.7.2014 03:35, William wrote:
Thanks. Could you please rename the option to
entry_cache_ssh_host_timeout, so that it's consistent with the rest of
the cache timeout options?
However, I can't quite work out how to access
On Tue, 2014-07-15 at 15:57 +0200, Jan Cholasta wrote:
On 11.7.2014 03:35, William wrote:
Thanks. Could you please rename the option to
entry_cache_ssh_host_timeout, so that it's consistent with the rest of
the cache timeout options?
However, I can't quite work out how to access
your requirements.
Any comments and advice welcome.
--
William will...@firstyear.id.au
From 539b74fb3eebf3e6f097a816ced8ade484d348c7 Mon Sep 17 00:00:00 2001
From: William Brown will...@firstyear.id.au
Date: Wed, 30 Apr 2014 16:29:32 +0930
Subject: [PATCH] Allow sss_cache to expire
On Tue, 2014-06-24 at 10:21 +0200, Jan Cholasta wrote:
Hi,
I'm terribly sorry for the late reply.
That's okay, I understand how it can be.
Could you add a sssd.conf option for the cache timeout?
Done. The option exists, and I updated the man page (?), and the default
option for this.
On Sun, 2014-06-29 at 20:22 +0930, William wrote:
On Tue, 2014-06-24 at 10:21 +0200, Jan Cholasta wrote:
Hi,
I'm terribly sorry for the late reply.
That's okay, I understand how it can be.
Could you add a sssd.conf option for the cache timeout?
Done. The option exists, and I
On Mon, 2014-05-26 at 09:19 +0200, Jan Cholasta wrote:
On 26.5.2014 03:41, William wrote:
I'm afraid there is no right thing to call ATM, as there is no support
for cache invalidation in SSH host code. I guess you'll have to
implement it yourself.
Off the top of my head, you need
use the dataExpire attribute, they use a different
attribute, which is why I opted to call ssh_known_host_expire.
--
William will...@firstyear.id.au
From f9ba86ca3c709aa7051d82568c235dbba38aebb0 Mon Sep 17 00:00:00 2001
From: William Brown will...@firstyear.id.au
Date: Wed, 30 Apr 2014 16:29:32
The way I read the SSH responder, calling
sysdb_update_ssh_known_host_expire() would be the right thing to do, but
I wonder if that would be enough or whether we'd need to call out to the
ssh responder to force writing out a new hosts file.
What you want to do is remove the entry from
function to call to expire a host?
Advice is appreciated.
--
William Brown will...@firstyear.id.au
From 03fb08a2fd8ca3046b8784b143300b191879e69b Mon Sep 17 00:00:00 2001
From: William Brown will...@firstyear.id.au
Date: Wed, 30 Apr 2014 16:29:32 +0930
Subject: [PATCH] Initial addition of ssh host cache
13 matches
Mail list logo
