Of course, we all like to have a life :)
On Fri Jan 09 2015 at 10:18:52 Ben Pfaff wrote:
> Thanks.
>
> Some background:
>
> I don't want to say "there will be a response within 24 hours" because
> I do like to take off weekends, and because I might easily judge
> something as not important even
Thanks.
Some background:
I don't want to say "there will be a response within 24 hours" because
I do like to take off weekends, and because I might easily judge
something as not important even though it was sent to the security
list. But I also don't want to say "there will be a response within
I change back to a more general statement, given that we can't really
guarantee a response time.
On Fri Jan 09 2015 at 09:54:03 Ben Pfaff wrote:
> I don't know what to say for response time. In general I expect it to
> be pretty fast for anything that is clearly urgent.
>
> On Fri, Jan 09, 2015
I don't know what to say for response time. In general I expect it to
be pretty fast for anything that is clearly urgent.
On Fri, Jan 09, 2015 at 09:48:11AM +1300, Andrew Kampjes wrote:
> Both good points, thanks Flavio.
> Ben, can you confirm what the expectation for response should be?
>
> Wil
Both good points, thanks Flavio.
Ben, can you confirm what the expectation for response should be?
Will swap those paragraphs too.
On 9 January 2015 at 05:11, Flavio Leitner wrote:
> On Thursday, January 08, 2015 11:14:40 AM Andrew Kampjes wrote:
> > Include more specific GPG recomendation usag
On Thursday, January 08, 2015 11:14:40 AM Andrew Kampjes wrote:
> Include more specific GPG recomendation usage.
> Add generalised rules for vulnerabilties.
>
> Signed-off-by: Andrew Kampjes
> ---
> SECURITY.md | 41 +
> 1 file changed, 29 insertions(+), 1
Include more specific GPG recomendation usage.
Add generalised rules for vulnerabilties.
Signed-off-by: Andrew Kampjes
---
SECURITY.md | 41 +
1 file changed, 29 insertions(+), 12 deletions(-)
diff --git a/SECURITY.md b/SECURITY.md
index d558d44..c85e594
