Addressing Security Issues in EE/EEU

mrjawapa · 2019-08-13 05:05:44

There is no doubt that Everybody Edits has some major security issues. That has been made very clear by the two recent data breaches.

If you're not aware of these data breaches, it's too late for you. All of your social media accounts, and likely your online banking accounts, have already been compromised.

The new team has had a lot of discussion, regarding these security flaws. We've come to the conclusion that it's just not worth fixing Everybody Edits.

Everybody Edits has existed for roughly 10 years. Through that time, there have been many developers who have made changes to the game's code. Each developer has their own way of coding. Some of these developers were not well versed in the coding language, and used bad practices.

As the game grew and new features were added, each developer stacked code on top of the previous code. Eventually this created a massive pile of code, filled with good and bad code, that is an absolute eye sore.

To put it simply: say you have 5 people who speak English. 1 doesn't have a tongue, and one speaks how peace types. Taking turns, they tell a story one scene at a time. Most of it understandable. Some of it leaves you scratching your head, wondering what the ****?

It was discussed whether we should start from scratch. Completely redo EE, and address all the major security flaws, and at a later date fix the minor issues. Two things stopped us from pursuing this.

1. If there is any chance of us releasing EEU in early 2019, we need to devote all our time and effort into EEU. Putting any resources towards reviving the original game would only delay the release date.

2. You guys won't give us money to work on EEU if there's nothing wrong with EE. The overall goal for this team is to do next-to-nothing and maximize profits via **** claims and false promises. Unfortunately, redoing the original game does not align with that goal.

We've been asked numerous times about the steps being taken to ensure EEU is not full of security holes. We think the community deserves to know. After all, it is your information on the line.

There was a lot of debate on what information was necessary to store, and how to store it. We wanted to find a solution that would prevent anyone from hacking the system.

We have yet to reach a conclusion, however, we have narrowed it down to a few ideas:

1. Instead of using an online database, we will keep hard files. When a user would attempt to login, a request would be sent to our HQ staff. This request would include the user inputted email and password. A certified member of our HQ staff will take that information, and find your file in a drawer. If the information provided in the login request message matches the information on file, the staff member will then approve the request.

2. As a more "common sense" approach to preventing anyone from hacking our online database, we decided to come up with a system that doesn't need to be hacked. Instead of encrypting the information we collect, using salt and pepper, cmd prompt, md5, hash, and bash, we decided information could be stored in plain text.

Plain text, and in plain sight.

We found that trying to hide the information only made people want to find it more.

There is still a lot of discussion to be had. Our plans may change as we move along, and we look forward to keeping the community notified. Our team aims to be as transparent as a brick wall possible. As updates are available, they will be released here, on the forums, as well as the blog.

See you in 6 months the worlds!

mrjawapa
Financial manager, web designer

Kkay, Bimps, Zumza, skullz17, MartenM, Kira, Snowester, coinage, Joeyjoey65, SirJosh3917

Anatoly · 2019-08-13 06:17:49

Thank you for the message

Regards
Anatoly

Fired cleaning boiii

peace · 2019-08-13 07:55:18

mrjawapa wrote:

2. As a more "common sense" approach to preventing anyone from hacking our online database, we decided to come up with a system that doesn't need to be hacked. Instead of encrypting the information we collect, using salt and pepper, cmd prompt, md5, hash, and bash, we decided information could be stored in plain text.
Plain text, and in plain sight.

if a hacker reads this he will insta hack EEU good job on postign it here

TaskManager · 2019-08-13 11:09:45

peace wrote:

mrjawapa wrote:
2. As a more "common sense" approach to preventing anyone from hacking our online database, we decided to come up with a system that doesn't need to be hacked. Instead of encrypting the information we collect, using salt and pepper, cmd prompt, md5, hash, and bash, we decided information could be stored in plain text.
Plain text, and in plain sight.
if a hacker reads this he will insta hack EEU good job on postign it here

damn peace if a hacker reads your post they will do exactly that, good job on helping the hacker do you want to be banned???

capasha, Snowester, PTU, Joeyjoey65, SirJosh3917, coinage

mrjawapa · 2019-08-13 22:24:06

peace wrote:

mrjawapa wrote:
2. As a more "common sense" approach to preventing anyone from hacking our online database, we decided to come up with a system that doesn't need to be hacked. Instead of encrypting the information we collect, using salt and pepper, cmd prompt, md5, hash, and bash, we decided information could be stored in plain text.
Plain text, and in plain sight.
if a hacker reads this he will insta hack EEU good job on postign it here

You obviously did not read the post.

If there is no system to hack, they cant hack it.

Norwee · 2019-08-13 22:29:57

Jawp y hacker hack?? :((

mrjawapa · 2019-08-13 23:15:15

NorwegianboyEE wrote:

Jawp y hacker hack?? (

Good question.

It's so they look cool to their friends. It's to force the staff to bow down to them. To assert their dominance, and make sure everyone knows they have a large <snip>.

Official Everybody Edits Forums

#1 2019-08-13 05:05:44

Addressing Security Issues in EE/EEU

#2 2019-08-13 06:17:49

Re: Addressing Security Issues in EE/EEU

#3 2019-08-13 07:55:18

Re: Addressing Security Issues in EE/EEU

#4 2019-08-13 11:09:45

Re: Addressing Security Issues in EE/EEU

#5 2019-08-13 22:24:06

Re: Addressing Security Issues in EE/EEU

#6 2019-08-13 22:29:57, last edited by Norwee (2019-08-13 22:30:03)

Re: Addressing Security Issues in EE/EEU

#7 2019-08-13 23:15:15, last edited by Tomahawk (2019-08-14 08:02:11)

Re: Addressing Security Issues in EE/EEU

Board footer