// Whenever the verification string has changed, publish the info node.
publishCapsNode();
// Resend presence. This manager will add the caps extension later.
PresenceManager presenceManager = xmppSession.getPresenceManager();
Presence lastPresence = presenceManager.getLastSentPresence();
Presence presence = new Presence();
presence.setError(lastPresence.getError());
presence.setFrom(lastPresence.getFrom());
presence.setPriority(lastPresence.getPriority());
presence.setLanguage(lastPresence.getLanguage());
presence.setShow(lastPresence.getShow());
presence.setStatus(lastPresence.getStatus());
presence.setTo(lastPresence.getTo());
xmppSession.send(presence);
}
}
}
});
xmppSession.addSessionStatusListener(new SessionStatusListener() {
@Override
public void sessionStatusChanged(SessionStatusEvent e) {
if (e.getStatus() == XmppSession.Status.CLOSED) {
jidInfos.clear();
cache.clear();
capsSent = false;
currentVerificationString = null;
}
}
});
xmppSession.addPresenceListener(new PresenceListener() {
@Override
public void handle(PresenceEvent e) {
Presence presence = e.getPresence();
if (!e.isIncoming()) {
if (isEnabled() && presence.isAvailable() && presence.getTo() == null) {
try {
// Synchronize on sdm, to make sure no features/identities are added removed, while computing the hash.
synchronized (serviceDiscoveryManager) {
if (currentVerificationString == null) {
recomputeVerificationString(HASH_ALGORITHM);
publishCapsNode();
}
// a client SHOULD include entity capabilities with every presence notification it sends.
presence.getExtensions().add(new EntityCapabilities(getNode(), HASH_ALGORITHM, currentVerificationString));
capsSent = true;
}
} catch (NoSuchAlgorithmException e1) {
logger.log(Level.WARNING, e1.getMessage(), e1);
}
}
} else {
EntityCapabilities entityCapabilities = presence.getExtension(EntityCapabilities.class);
if (entityCapabilities != null) {
synchronized (EntityCapabilitiesManager.this) {
Verification verification = new Verification(entityCapabilities.getHashingAlgorithm(), entityCapabilities.getVerificationString());
// Check if the verification string is already known.
if (entityCapabilities.getHashingAlgorithm() != null && cache.containsKey(verification)) {
InfoNode infoNode = cache.get(verification);
// If its known, just update the information for this entity.
jidInfos.put(presence.getFrom(), infoNode);
} else {
// 1. Verify that the <c/> element includes a 'hash' attribute. If it does not, ignore the 'ver'
String hashAlgorithm = entityCapabilities.getHashingAlgorithm();
if (hashAlgorithm != null) {
try {
// 3. If the value of the 'hash' attribute matches one of the processing application's supported hash functions, validate the verification string by doing the following:
MessageDigest messageDigest = MessageDigest.getInstance(entityCapabilities.getHashingAlgorithm());
try {
// 3.1 Send a service discovery information request to the generating entity.
// 3.2 Receive a service discovery information response from the generating entity.
InfoNode infoDiscovery = serviceDiscoveryManager.discoverInformation(presence.getFrom(), entityCapabilities.getNode() + "#" + entityCapabilities.getVerificationString());
// 3.3 If the response includes more than one service discovery identity with the same category/type/lang/name, consider the entire response to be ill-formed.
// 3.4 If the response includes more than one service discovery feature with the same XML character data, consider the entire response to be ill-formed.
// => not possible due to java.util.Set semantics and equals method.
// If the response had duplicates, just check the hash.
// 3.5 If the response includes more than one extended service discovery information form with the same FORM_TYPE or the FORM_TYPE field contains more than one <value/> element with different XML character data, consider the entire response to be ill-formed.
List<String> ftValues = new ArrayList<>();
for (DataForm dataForm : infoDiscovery.getExtensions()) {
DataForm.Field formType = dataForm.findField("FORM_TYPE");
// 3.6 If the response includes an extended service discovery information form where the FORM_TYPE field is not of type "hidden" or the form does not include a FORM_TYPE field, ignore the form but continue processing.
if (formType != null && formType.getType() == DataForm.Field.Type.HIDDEN && !formType.getValues().isEmpty()) {
List<String> values = new ArrayList<>();
for (String value : formType.getValues()) {
if (values.contains(value)) {
// ill-formed
return;
}
values.add(value);
}
String value = formType.getValues().get(0);
if (ftValues.contains(value)) {
// ill-formed
return;
}
ftValues.add(value);
}
}
// 3.7 If the response is considered well-formed, reconstruct the hash by using the service discovery information response to generate a local hash in accordance with the Generation Method).
String verificationString = EntityCapabilities.getVerificationString(infoDiscovery, messageDigest);
// 3.8 If the values of the received and reconstructed hashes match, the processing application MUST consider the result to be valid and SHOULD globally cache the result for all JabberIDs with which it communicates.
if (verificationString.equals(entityCapabilities.getVerificationString())) {
cache(new Verification(hashAlgorithm, verificationString), infoDiscovery);
}
jidInfos.put(presence.getFrom(), infoDiscovery);
// 3.9 If the values of the received and reconstructed hashes do not match, the processing application MUST consider the result to be invalid and MUST NOT globally cache the verification string;
} catch (XmppException e1) {
logger.log(Level.WARNING, e1.getMessage(), e1);
}
} catch (NoSuchAlgorithmException e1) {
// 2. If the value of the 'hash' attribute does not match one of the processing application's supported hash functions, do the following:
try {
// 2.1 Send a service discovery information request to the generating entity.
// 2.2 Receive a service discovery information response from the generating entity.
InfoNode infoNode = serviceDiscoveryManager.discoverInformation(presence.getFrom(), entityCapabilities.getNode());
// 2.3 Do not validate or globally cache the verification string as described below; instead, the processing application SHOULD associate the discovered identity+features only with the JabberID of the generating entity.
jidInfos.put(presence.getFrom(), infoNode);
} catch (XmppException e2) {
logger.log(Level.WARNING, e2.getMessage(), e2);
}
}
}