161
edits
Difference between revisions of "Tech pages/OX"
Jump to navigation
Jump to search
no edit summary
m |
|||
| Line 6: | Line 6: | ||
There are different people with different background knowledge about OpenPGP / | There are different people with different background knowledge about OpenPGP / | ||
GnuPG. XMPP OX should be able to integrate in clients which hides the technical | GnuPG. XMPP OX should be able to integrate OpenPGP in clients which hides the technical | ||
details of OpenPGP to the user. But, XMPP OX should also useable for technical | details of OpenPGP to the user. But, XMPP OX should also useable for technical | ||
people which may have a OpenPGP Smartcard or a Token. | people which may have a OpenPGP Smartcard or a Token. | ||
At the end of the day, the different client applications should be able to share information and messages. | |||
messages. | |||
== OpenPGP via GnuPG == | == OpenPGP via GnuPG == | ||
There are two use cases to create the key material. | There are two use cases to create the key material. | ||
Users with technical background may have his own key or prefer to | Users with technical background may have his own key or prefer to generate his | ||
own key via GnuP. This is '''not''' a question about trust the gnupg application or trust the xmpp | own key via GnuP. This is '''not''' a question about trust the gnupg application or trust the xmpp | ||
client application, this is more a habit of the user. | client application, this is more a habit of the user. | ||
Non-technical users may prefer that the XMPP client acts on behalf of the user | |||
and will generate the key material. Even, '''without''' asking the user a lot of questions. | |||
=== Generating key === | === Generating key === | ||
| Line 28: | Line 30: | ||
</pre> | </pre> | ||
Generating the key within the XMPP is up to the developer. | Generating the key within the XMPP client is up to the developer. | ||
It recommend to have such a option, to make the on boarding for non technical | It's recommend to have such a option, to make the on boarding for non technical | ||
people easier. | people easier. | ||
| Line 39: | Line 41: | ||
The user should be able to manage his key pair. Also, the XMPP Client should be | The user should be able to manage his key pair. Also, the XMPP Client should be | ||
able to assistant, by adding a UID. | able to assistant, by adding a UID for the XMPP Account. | ||
A key can look like this: | A key can look like this: | ||
| Line 63: | Line 65: | ||
</pre> | </pre> | ||
* If there is a private key with an existing UID for the account, just use it. | |||
* If there is a private key, but there is no private key with a UID of the account, ask the user to add a UID | |||
* If there is no private key, create one for the XMPP account. | |||
=== Export a public key === | === Export a public key === | ||