From 9c3bd99e07e5c0d9fea6e24f173e9c4b829b87de Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Sun, 1 Jan 2017 12:53:08 -0600 Subject: [PATCH] XEP-0379: Fix some DTD issues. --- xep-0379.xml | 25 ++++++++++++++----------- xep.ent | 1 + 2 files changed, 15 insertions(+), 11 deletions(-) diff --git a/xep-0379.xml b/xep-0379.xml index be7cbcdf..0c24637b 100644 --- a/xep-0379.xml +++ b/xep-0379.xml @@ -28,6 +28,12 @@ georg@op-co.de georg@yax.im + + 0.1.1 + 2017-01-01 + ssw +

Minor DTD and formatting fixes.

 + 0.1.0 2016-07-20 @@ -165,7 +171,7 @@ https://yax.im/i/romeo/montague.net/1tMFqYDdKhfe2pwp/Romeo+Montague

Romeo Montague has invited you to chat

-

Add Romeo Montague

+

Add "Romeo Montague"

If this link does not work, you need to install and configure an XMPP client. Please visit this page again afterwards. Choose one of these for your Tomato OS:

@@ -285,22 +291,19 @@ https://yax.im/i/romeo/montague.net/1tMFqYDdKhfe2pwp/Romeo+Montague

As the authentication token grants automatic addition to Romeo's roster and automatic approval of presence subscription, the token SHOULD be created with a cryptographically secure random - number generator See for example getrandom(2), - SecureRandom + number generator See for example getrandom(2), + SecureRandom or /dev/urandom. More information about the randomness requirements for security can be found in &rfc4086; and provide sufficient entropy to make brute-force attacks infeasible. It is suggested to generate at least 80 bits of entropy, and to use an encoding that can be easily encoded as part of an URI (e.g. Base-32).

It is possible to use a different token - generation scheme like SAMLSecurity Assertion Markup - Language (SAML) <https://www.oasis-open.org/standards#samlv2.0> - or JWT (RFC - 7519RFC 7519: JSON Web Token (JWT) <http://tools.ietf.org/html/rfc7519>). In - such a case, the issuer must ensure a comparable security level - and limit token reuse.

+ generation scheme like &saml; or JWT (&rfc7519;). + In such a case, the issuer must ensure a comparable security level and + limit token reuse.

To limit the potential for abuse, the token SHOULD be limited in as follows:

diff --git a/xep.ent b/xep.ent index 83cb2f15..43301f8a 100644 --- a/xep.ent +++ b/xep.ent @@ -650,6 +650,7 @@ THE SOFTWARE. RFC 6763 RFC 6763: DNS-Based Service Discovery <http://tools.ietf.org/html/rfc6763>." > RFC 6920 RFC 6920: Naming Things with Hashes <http://tools.ietf.org/html/rfc6920>." > RFC 7081 RFC 7081: CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) <http://tools.ietf.org/html/rfc7081>." > +RFC 7519 RFC 7519: JSON Web Token (JWT) <http://tools.ietf.org/html/rfc7519>." > RFC 7572 RFC 7572: Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant Messaging <http://tools.ietf.org/html/rfc7572>." > RFC 7595 RFC 7595: Guidelines and Registration Procedures for URI Schemes <http://tools.ietf.org/html/rfc7595>." > RFC 7613 RFC 7613: Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords<http://tools.ietf.org/html/rfc7613>." >