File

mod_tokenauth: Switch to new token format (invalidates existing tokens!) The new format has the following properties: - 5 bytes longer than the previous format - The token now has separate 'id' and 'secret' parts - the token itself is no longer stored in the DB, and the secret part is hashed - The only variable length field (JID) has been moved to the end - The 'secret-token:' prefix (RFC 8959) is now included Compatibility with the old token format was not maintained, and all previously issued tokens are invalid after this commit (they will be removed from the DB if used).

# mod_scansion_record on host 'localhost' recording started 2022-07-26T21:39:55Z

[Client] Romeo
	password: password
	jid: juliet@localhost/UaksS4M1xYZB

-----

Romeo connects

Romeo sends:
	<iq xml:lang='en' type='get' id='bNBJLtpIJXpq'>
		<pubsub xmlns='http://jabber.org/protocol/pubsub'>
			<items node='storage:bookmarks'/>
		</pubsub>
	</iq>

Romeo receives:
	<iq id='bNBJLtpIJXpq' type='error'>
		<error type='cancel'>
			<item-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
		</error>
	</iq>

Romeo disconnects

# recording ended on 2022-07-26T21:40:45Z