I am not connected to nor is the server, so I dont know why it is looking there at all. Which I can not figure out for the life of me. XMPP Error: iq error 404 from : unspecified Third, if in Trillian, just did this right this second, latest versions of everything involved, I am connected only to jive, and show the status window for that connection, and watch it, and then search for contacts, this is what I get: This is actually our plan right now & are half way there. Second, and I think this was mentioned, but just to hit it again, you can add your server’‘s ability to talk to AIM & MSN gateways and still keep your clients locked-down to using only jabber, and still have them talk to those outside your org’’ that way. The built-in encryption is great between Trillian users, but of course that is a thin slice of the contacts on my roster. It ought to & I can not for the life of me figure out why tehy dont. I use GAIM on Linux & am falling in love with it also. First, love Trillian, been using it for a few years, worth the money for Pro. We're working internally to address the incident and making every effort to ensure nothing like it happens again.Just wanted to add a snippet of my experience. Please feel free to contact us directly with any additional questions or concerns, and please accept our sincere apologies. Next steps?īecause the impacted machine has been taken offline completely and will stay offline, the major ongoing concern for customers is if your blog or forum password was shared with another service, including Trillian itself. Practice password safety by always using a different password for each site and taking advantage of a password manager to make doing so bearable. While the stolen passwords were hashed, modern computational power makes targetting a specific password well within the realm of possibility. In addition, if you used the same password on our forums or on our blog as you do anywhere else on the internet, we also urge you to also change that password ASAP. Instructions for changing your Trillian password can be found here. If you used the same password on our forums or blog as you do Trillian itself, we urge you to change your Trillian password ASAP. In addition to blog and forum data, your Trillian username and email may have been leaked - however, the database containing them did not contain password information. Because the blog and forums were running third-party code in the form of Wordpress and vBulletin, we carefully isolated them from the rest of our network many years ago so the main Trillian infrastructure wasn't impacted. Only those customers who had specifically registered to post comments on our blog or participate on our forums are at risk of password theft. If your information for either our blog or forums was taken, you should have received, or will receive, an email from us notifying you of the incident and pointing you to this FAQ. The resulting likelihood of the data being useful to an attacker is therefore much lower unless you've used the same password for many years across multiple sites. Because both of these services had already been deprecated and were only kept online for archival purposes, most of the data was anywhere from 3 to 14 years old. The information included salted MD5 hashed passwords for both our Wordpress blog and vBulletin forums but not for Trillian itself. The vulnerability was specific to our deployment of vBulletin, and the intruders used this vulnerability to also extract information from our Wordpress blog and a handful of other marketing-centric databases that contained Trillian usernames and email addresses. We became aware of the breach the next day, July 5th, 2016, and immediately shut down the machine and retired it permanently for further forensic analysis. On July 4th, 2016, a security breach and data disclosure related to a single server that powered the now-retired blog and forums occurred. However, the data impacted wouldn't have been any different and so our below instructions remain valid for those of you whose blog and/or forum accounts were a part of the leak. We are still investigating this to confirm but the safest bet is to assume it's correct. July 16th Update: Some reports point to an earlier date of intrusion, December 2015. We've updated the paragraphs below to accurately reflect our knowledge as of this writing. No password information was stored or leaked in this case. July 15th Update: Additional investigation has revealed that a subset of Trillian usernames and emails were also taken by the intruders.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |