Squatting Monk wrote...
Lazarus Magni wrote...
I have repeated this over and over again. I am grateful for the community submitted security systems, and indeed would not remove them even with the MS back, but they didn't fix the problem. They don't apply retroactively, and for PWs like mine that have almost 10 years of players in my vault, that really hurts.
There's an easy fix for this. Back up your servervault, then clear out every player who doesn't have a CDKey registered in your database. If an old player comes back and discovers his characters are gone, you can always restore them after confirming his identity. Granted, this won't stop malicious players from logging in as that player and making a new character, but it will mitigate the greatest of the harms, which would be having existing characters messed with.
Slightly less easy but even better: add every player in your servervault to the database, but give them a NULL CDKey. This way, anyone who logs in as that player will be automatically rejected. When the player comes back, you can fix his CDKey then, allowing him to log in like normal.
That's why Funky posted his scripts for everyone. Even a non-scripter can follow his instructions and have a functional, if basic, security system. It doesn't require any expertise beyond knowing how to follow instructions.
You are quite wrong here on all accounts. I disabled all old accounts exactly because of this. So now when I have a returning player, and they say I am so and so, how do I verify that? Because I have been involved in the community the whole time I have ways to gauge the likelyhood of this being legitimate (I remember old players and who they ran with.) But this is not fool proof. There I just admitted publically a security flaw for my PW. Does that make you happy? I am willing to do that, why can Bioware be forthcoming to it's players as to why they can no longer contribute to the security and well being for the PWs that were made from their platform?
And Funky's system? Yes it is genius. I am no slouch, but I could not get it working. And should a volunteer really be responsible for providing tech support for this? I was lucky to have a truly gifted scripter willing to work with us to get this working right. But out of the box, so to speak, no... I could not make it work on my own...
And...
It’s not a problem I alone have. It is an online community problem as the direct result of the shut down of the Master server. Yes it’s true there have always been other issues, but no it’s not true this occurrence has not exasperated them
No one to this date has really explained why this was needed. As I pointed out before, when serious haks occur, usually there is a financial motive behind them. AKA the hacked website is storing financial data of their users. This was not the case for Bioware. Furthermore, usually those websites are back on line within days if not hours, and the security hole plugged.
No real reason has been given for not bringing the server back on line. And yes, you ask me if I would prefer silence to some people speaking out of turn? The answer is yes. Because that silence would clearly indicate the assumptions are correct.
What assumption? That being… Bioware used this as an excuse to do their best to kill off the on line community. Due to the resilience of the community, it didn’t do it 100%. None the less the situation is still not good, and I would like to know why.
Why would you feel inclined to let people’s works of art become subject to any old jerk who doesn’t like your PW, or something you said? Why would you not recognize PW’s as art and want to preserve their integrity?
I am not just speaking as a PW owner on this. I am also speaking as a player. Even when I was only a player, I still was a contributor (as a player) to that work of art.
The present state of things is not right, and we deserve at the very least a legitimate reason for that from the developer, and better yet a collaborative effort with them for a lasting resolution.