On Thu, 2014-09-18 at 14:20 -0400, Simo Sorce wrote:
On Thu, 18 Sep 2014 13:59:34 -0400
Nathaniel McCallum npmccal...@redhat.com wrote:
On Thu, 2014-09-18 at 14:00 +0200, Petr Vobornik wrote:
On 15.9.2014 21:08, Nathaniel McCallum wrote:
On Thu, 2014-08-28 at 22:54 -0400, Nathaniel
On 15.9.2014 21:08, Nathaniel McCallum wrote:
On Thu, 2014-08-28 at 22:54 -0400, Nathaniel McCallum wrote:
This prevents any local attempt at rapid token code replay. If two
token codes hit the system at roughly the same moment, only the
first write will succeed. All subsequent authentications
On Thu, 2014-09-18 at 14:00 +0200, Petr Vobornik wrote:
On 15.9.2014 21:08, Nathaniel McCallum wrote:
On Thu, 2014-08-28 at 22:54 -0400, Nathaniel McCallum wrote:
This prevents any local attempt at rapid token code replay. If two
token codes hit the system at roughly the same moment, only
On Thu, 18 Sep 2014 13:59:34 -0400
Nathaniel McCallum npmccal...@redhat.com wrote:
On Thu, 2014-09-18 at 14:00 +0200, Petr Vobornik wrote:
On 15.9.2014 21:08, Nathaniel McCallum wrote:
On Thu, 2014-08-28 at 22:54 -0400, Nathaniel McCallum wrote:
This prevents any local attempt at rapid
On Thu, 2014-08-28 at 22:54 -0400, Nathaniel McCallum wrote:
This prevents any local attempt at rapid token code replay. If two
token codes hit the system at roughly the same moment, only the
first write will succeed. All subsequent authentications will fail.
This obviates the need for an
On Thu, 2014-08-28 at 22:54 -0400, Nathaniel McCallum wrote:
This prevents any local attempt at rapid token code replay. If two
token codes hit the system at roughly the same moment, only the
first write will succeed. All subsequent authentications will fail.
This obviates the need for an
This prevents any local attempt at rapid token code replay. If two
token codes hit the system at roughly the same moment, only the
first write will succeed. All subsequent authentications will fail.
This obviates the need for an OTP authentication lock.
