On 09/05/2013 06:25 AM, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
1. The handling of the 'key' option is insecure. It should probably be
treated like a password (hidden from logs, etc). However, in this case,
it is
On 10/01/2013 11:00 PM, Nathaniel McCallum wrote:
On Thu, 2013-09-05 at 12:19 +0200, Petr Viktorin wrote:
On 09/05/2013 06:38 AM, Nathaniel McCallum wrote:
3. I had to make the 'id' option optional to make the uuid
autogeneration work in otp-add. However, this has the side-effect that
'id' is
On Thu, 2013-09-05 at 12:19 +0200, Petr Viktorin wrote:
On 09/05/2013 06:38 AM, Nathaniel McCallum wrote:
3. I had to make the 'id' option optional to make the uuid
autogeneration work in otp-add. However, this has the side-effect that
'id' is now optional in all the other commands. This is
On 09/13/2013 08:39 PM, Dmitri Pal wrote:
On 09/13/2013 11:55 AM, Petr Vobornik wrote:
On 09/05/2013 06:25 AM, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
snip
Some additional findings:
1. Inconsistency:
On 13.9.2013 10:07, Jan Cholasta wrote:
On 5.9.2013 06:25, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
1. The handling of the 'key' option is insecure. It should probably be
treated like a password (hidden from logs,
On 5.9.2013 06:25, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
1. The handling of the 'key' option is insecure. It should probably be
treated like a password (hidden from logs, etc). However, in this case,
it is
I'm sorry for the late reply, I got caught up in other work and forgot
about this thread.
On 09/05/2013 03:31 PM, Nathaniel McCallum wrote:
On Thu, 2013-09-05 at 12:19 +0200, Petr Viktorin wrote:
On 09/05/2013 06:38 AM, Nathaniel McCallum wrote:
On Thu, 2013-09-05 at 00:25 -0400, Nathaniel
On Thu, 2013-09-12 at 13:48 +0200, Petr Viktorin wrote:
I'm sorry for the late reply, I got caught up in other work and forgot
about this thread.
On 09/05/2013 03:31 PM, Nathaniel McCallum wrote:
On Thu, 2013-09-05 at 12:19 +0200, Petr Viktorin wrote:
On 09/05/2013 06:38 AM, Nathaniel
On 09/05/2013 06:25 AM, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
snip
Some additional findings:
1. Inconsistency: 'ipatokenowner' in command output should be normalized
the same way as 'manager' in user plugin
On 09/12/2013 09:15 PM, Dmitri Pal wrote:
On 09/12/2013 07:28 AM, Petr Vobornik wrote:
Qs:
a. Do we have some use cases for adding internal OTP? I wonder which
otp-add options are essential (ipatokenvendor, ipatokenmodel,
ipatokenserial, ipatokenotpkey, ipatokenotpalgorithm,
ipatokenotpdigits,
On 09/12/2013 07:28 AM, Petr Vobornik wrote:
Qs:
a. Do we have some use cases for adding internal OTP? I wonder which
otp-add options are essential (ipatokenvendor, ipatokenmodel,
ipatokenserial, ipatokenotpkey, ipatokenotpalgorithm,
ipatokenotpdigits, ipatokentotpclockoffset,
On 09/13/2013 11:55 AM, Petr Vobornik wrote:
On 09/05/2013 06:25 AM, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
snip
Some additional findings:
1. Inconsistency: 'ipatokenowner' in command output should be
On 09/13/2013 12:19 PM, Petr Vobornik wrote:
ipatokenvendor
will be us
, ipatokenmodel,
IPA?
ipatokenserial
Generated
, ipatokenotpkey
Generated
, ipatokenotpalgorithm
Uses default TOTP we do not support more for now. In future it will be a
global policy I assume.
,
I've started the work on OTP UI and found few issues in this patch:
1. api.txt is not regenerated. Run ./makeapi. Same issue is in patch #15
and #16.
2. python-qrcode is missing in BuildRequires
3. minor: would be nice if attribute names in `takes_params` and
`default_attributes` would have
On 09/12/2013 03:38 PM, Nathaniel McCallum wrote:
On Thu, 2013-09-12 at 13:48 +0200, Petr Viktorin wrote:
I'm sorry for the late reply, I got caught up in other work and forgot
about this thread.
On 09/05/2013 03:31 PM, Nathaniel McCallum wrote:
On Thu, 2013-09-05 at 12:19 +0200, Petr
On 09/05/2013 06:25 AM, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
1. The handling of the 'key' option is insecure. It should probably be
treated like a password (hidden from logs, etc). However, in this case,
it
On 09/07/2013 06:28 PM, Simo Sorce wrote:
On Thu, 2013-09-05 at 00:38 -0400, Nathaniel McCallum wrote:
On Thu, 2013-09-05 at 00:25 -0400, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
1. The handling of the 'key'
On Thu, 2013-09-05 at 00:38 -0400, Nathaniel McCallum wrote:
On Thu, 2013-09-05 at 00:25 -0400, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
1. The handling of the 'key' option is insecure. It should probably be
On 09/05/2013 06:38 AM, Nathaniel McCallum wrote:
On Thu, 2013-09-05 at 00:25 -0400, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
1. The handling of the 'key' option is insecure. It should probably be
treated like a
On Thu, 2013-09-05 at 12:19 +0200, Petr Viktorin wrote:
On 09/05/2013 06:38 AM, Nathaniel McCallum wrote:
On Thu, 2013-09-05 at 00:25 -0400, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
1. The handling of the
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
1. The handling of the 'key' option is insecure. It should probably be
treated like a password (hidden from logs, etc). However, in this case,
it is binary, so I'm not quite sure how to do that.
On Thu, 2013-09-05 at 00:25 -0400, Nathaniel McCallum wrote:
This patch has a few problems that I'd like some help with. There are a
few notes here as well.
1. The handling of the 'key' option is insecure. It should probably be
treated like a password (hidden from logs, etc). However, in
22 matches
Mail list logo
