@jordan31 @josias Not unless someone didn't do their ssl layer right. It's possible, of course, but not likely. Your ISP isn't going to be decrypting anything, though. It doesn't have the CA, or the key. If it was that easy, the FBI wouldn't have had to put Lavabit out of business to get their private […]
@jordan31 @josias @ray Not by any means saying trillian was an examplar - but for its time, it was pretty cool. As long as all you have to do is set up your various instance accounts in the client, how the server handles each one (at least to this extent) is immaterial, as long as […]
@jordan31 @josias @ray After thinking about it a bit, I think there's solution that we might have overlooked. Y'all remember trillian, or is that too old for you? If this behavior of accounts is consolidated on the client side, (ie: specifiying that you're using this account for x service, this other account for y service, […]
@ray @jordan31 @josias On the other hand, we're currently duplicating the security issues for each and every instance we host, by separate accounts for each. So, it might be a case of half a dozen of one, six of the other. I'm not sure - but I sure don't want just anyone who visits the […]
3 comments
Comment by Chris on May 3, 2012 at 12:09 am
Just out of curiosity, what was the cause of the problem?
Comment by RazorsKiss on May 4, 2012 at 3:59 pm
SQL injection, back from when Dreamhost had a small security breach on my server.
I didn’t catch one file when I cleaned it up last time, which self-multiplied and re-infected my site.
Comment by Chris on May 5, 2012 at 7:48 pm
Ugh, yeah SQL injection can be a problem. Glad you got it taken care of!