Regards,
David
The XMPP login name requires that you always include @gmail.com at the
end of the user name for it to work.
XMPP library does an SRV lookup on gmail.com for the XMPP service which
returns talk.google.com as the XMPP server.
As a result, if you do jan...@janedomain.com as you XMPP login to
GoogleChat it will not work, try jan...@janedomain.com@gmail.com.
Hopefully, Jabber.Net library can properly parse it as a valid JID for
login.
<JabberHost>talk.google.com</JabberHost>
The line above is case sensitive. I cannot guarantee that it will work
because I never got a chance to properly test it. Please let me know if
you are successful.
We make the assumption that the certificate exchange is done through a
secure out-of-band channel independent of socialvpn. For example,
PGP-signed email could be one method. We are currently in making that
process easier and more intuitive for the next release.
Seriously, there is often a tension between making a feature-filling
software and doing research that is interesting.
We've talked abou PGP keyservers in the past, and we certainly haven't
ruled it out, we just haven't implemented it.
There can still be an issue of identifying trusted keys if you don't
have a path of trust to the key you get from the server, so you'll
still need to exchange fingerprints (but in reality, I guess few
bother to be so careful).
Glad this is useful to you. Keep the comments coming and code
contributions would be more than welcome!
Best,
> --
> You received this message because you are subscribed to the Google Groups "acis.p2p.users" group.
> To post to this group, send email to acisp2...@googlegroups.com.
> To unsubscribe from this group, send email to acisp2pusers...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/acisp2pusers?hl=en.
>
>
--
P. Oscar Boykin http://boykin.acis.ufl.edu
Assistant Professor, Department of Electrical and Computer Engineering
University of Florida