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' 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. Passing it as a
>>> command line option may be nice for scripting, but is potentially a
>>> security problem if it ends up in bash.history. It would also be nice if
>>> the encoding were base32 instead of base64, since nearly all the OTP
>>> tools use this encoding.
>>>
>>> 2. The 'key' option also appears in otp-find. I'd like to suppress this.
>>> How?
>>>
>>> 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 particularly bad
>>> in the case of otp-del, where calling this command with no ID
>>> transparently removes all tokens. How can I make this optional for
>>> otp-add but required for all other commands?
>>>
>>> 4. otp-import is not implemented. I spent a few hours looking and I
>>> didn't find any otp tool that actually uses this xml format for
>>> exporting. Should we implement this now or wait until someone can
>>> actually export data to us?
>>>
>>> 5. otp-del happily deletes the last token for a user. How can I find out
>>> the dn of the user executing the command? Also, what is the right
>>> exception to throw in pre_callback()?
>>>
>>> 6. user-show does not list the associated tokens for this user. Do we
>>> care? It is a single search: otp-find --owner npmccallum.
>>>
>>> 7. otp-add only prints the qr code if the --qrcode option is specified.
>>> This is for two reasons. First, and most importantly, the qr code
>>> doesn't fit on a standard 24x80 terminal. I wanted to avoid dumping
>>> garbage on people's screens by default. Second, you may not always want
>>> the qr code output (like for a hard token or manual code entry).
>>
>> 8. If a user is deleted, the user's assigned tokens are left unmodified.
>> That is *not* to say they are orphaned. The owner attribute retains a dn
>> to an invalid user. This also means that otp-find --owner=deletedUser
>> will fail since we can't look up the deleted user. How does dirsrv
>> handle this for other relationships?
> 
> Elsewhere we use the referential integrity plugin, but I am not entirely
> sure it will work here ?
> 
> Simo.

IMO it should. We will probably also need to add new indices in order to let
Referential Integrity work efficiently.

See https://fedorahosted.org/freeipa/ticket/2866 for more information how was
this done in the past. Related thread on freeipa-devel:
http://www.redhat.com/archives/freeipa-devel/2012-September/msg00027.html

I can provide more information if needed.

Martin

_______________________________________________
Freeipa-devel mailing list
Freeipa-devel@redhat.com
https://www.redhat.com/mailman/listinfo/freeipa-devel

Reply via email to