Thanks! Closing because related to issue #3.
SMIME Certs in Contacts
Good work, so far! Two requests follow…
REQUEST #1: X509 in vCard
X509 PROPERTY inclusion IETF description:
MAKE CONFIGURATION EASY: REQUEST EMAIL ADDRESS, FIRST AND DO LOOKUP; AUTOMATICALLY FILLING IN CONFIGURATION INFO ON NEXT SCREEN. (YOU CURRENTLY DO IT “BACKWARDS”… ASK FOR CONFIG… THEN ASK FOR A NAME or EMAIL ADDRESS.)
REQUEST #2: Autodiscovery RFC6764
Locating Services for Calendaring Extensions to
WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV)
ALSO, A SUGGESTION: I saw somewhere that you use Baikal for testing.
Might I suggest DAViCal for testing? It’s much more stable and complete.
The second one is a duplicate of #148
Regarding the draft document about SMIME Capabilities: How should such information be synchronized with the Android Contacts provider although there’s no support on Android’s content provider side and for what reason? Applications couldn’t make use of it anyway.
Regarding the draft document about SMIME Capabilities: How should such information be synchronized with the Android Contacts provider although there’s no support on Android’s content provider side and for what reason? <<<
First, and foremost, Contacts is the proper place to include S/MIME certs so that the email can be properly signed and encrypted without doing any ‘extra work’ on the part of the user. The cert gets picked at the time the user addresses the email.
I know for sure that other systems like MS Outlook already include X509 in its vcards. I haven’t checked the latest iPhone.
I realize that, at this point in time, Android Contacts does not support storage of certs. But, it was only recently that they even included the ability to do S/MIME. SO,… IMHO,… You’ll be ready for it when they release a version of Android that will include S/MIME storage in the Contacts. (It doesn’t make logical sense to manage certs, separately. P7x certs are included in every S/MIME email… and should be detected by the Android mail system to insert it into the contact.
If “Google” (aka whoever) does NOT include the function, mark my words: Someone else will or already has. For example, Touchdown, Moxier, K9, etc…
AND… CORRECTION: I provided the wrong RFC for the X509 vcard attribute.
While I’d like to have user certificate in the address book, DAVdroid can only sync what’s defined by the “Contacts Contract”:
All other item types would be application-specific, i.e. when DAVdroid would define such rows, other applications wouldn’t be able to access them because the names and entries would not be standardized.
So I’ll close this as “not possible at the moment”. Maybe there will be a CommonDataKind for this in future Android APIs.
I haven’t confirmed this, but, I think you can still do it. The ability or inability to use it is irrelevant at this point – by the “builtin” mail program. However, I haven’t confirmed this, either; But, third parties could probably pick it up/recognize it, too.
But, yes, you’d probably have to create a ContentProvider. Gotta look into the existing mail program to see how they’re handling the Certs, now.
QUOTE: Data kinds
Data is a generic table that can hold any kind of contact data. The kind of data stored in a given row is specified by the row’s MIMETYPE value, which determines the meaning of the generic columns DATA1 through DATA15. For example, if the data kind is Phone.CONTENT_ITEM_TYPE, then the column DATA1 stores the phone number, but if the data kind is Email.CONTENT_ITEM_TYPE, then DATA1 stores the email address. Sync adapters and applications can introduce their own data kinds.