Forum :: Announcements :: EO Server Backdoor Warnings

No one cares about your 2's drama... this shits funny though I mean the "elevation" shit. 


So this only works if your "elevation" ... couldn't the creator just make that name then. XD

I'm assuming there is other "hidden features".. 

---
http://www.ctronic.ga
http://www.tsu.co/Deltro
https://www.reverbnation.com/deltro9

Pine posted: (9th Jan 2012, 04:01 am)

Yes it is, I'm Banana.

Elevations trying to cover himself up: eosource.net && http://eosource.net/forum/showthread.php?tid=320

Today, 02:01 PM Post: #12

elevations   Administrator Posts: 69 Joined: Oct 2011  Reputation: 2

RE: Sausage It is not a backdoor. Sausage somehow debugged the eosource code and stumbled upon a broken forgotten command probably using his own backdoors in the EOSERV code. It was command that hollow used in hollowfication online that hollow had forgot to remove. We apoligize for the confusion but Sausage is obviously so quick to jump into peoples codes using debugging programs just to find any type of evidence to benefit his precious eoserv as he knows its dieing.

---
http://www.ctronic.ga
http://www.tsu.co/Deltro
https://www.reverbnation.com/deltro9

OH SHITNUTZ! I never knew, i thought it was a fake sausage :(

kodyt posted: (9th Jan 2012, 04:07 am)

Today, 02:01 PM Post: #12

elevations   Administrator Posts: 69 Joined: Oct 2011  Reputation: 2

RE:Sausage It is not a backdoor. Sausage somehow debugged the eosource code and stumbled upon a broken forgotten command probably using his own backdoors in the EOSERV code. It was command that hollow used in hollowfication online that hollow had forgot to remove. We apoligize for the confusion but Sausage is obviously so quick to jump into peoples codes using debugging programs just to find any type of evidence to benefit his precious eoserv as he knows itsdieing.

---
¨°º¤ø„º°¨ Exile Studios ¨°º„ø¤º°¨

Deathx posted: (9th Jan 2012, 04:10 am)

kodyt posted: (9th Jan 2012, 04:07 am)

Today, 02:01 PM Post: #12

elevations   Administrator Posts: 69 Joined: Oct 2011  Reputation: 2

RE:Sausage It is not a backdoor. Sausage somehow debugged the eosource code and stumbled upon a broken forgotten command probably using his own backdoors in the EOSERV code. It was command that hollow used in hollowfication online that hollow had forgot to remove. We apoligize for the confusion but Sausage is obviously so quick to jump into peoples codes using debugging programs just to find any type of evidence to benefit his precious eoserv as he knowsitsdieing.

That's funny. You can see the shit plain as day just skimming through the hex of the binary. Plus like #user is really that hard to guess lol.

---
http://www.ctronic.ga
http://www.tsu.co/Deltro
https://www.reverbnation.com/deltro9

Well it depends on the Character name too, that uses the command :P

Let's look at this from both point of views so we don't become biased here.

1. The backdoor was added there on purpose so that elevations/hollow could steal valuable information from others. Well, this just makes elevations/hollow look like jackasses because they want other people's information. It also makes them look like fools because Elevations brags about it to Apollo, and Sausage finds it in 3seconds :P

2. The command was left there on accident because Hollow forgot to remove it before releasing. If you can't even notice unwanted commands in your source, then you might have a huge glob of shit and might not be a worthy programmer. Organization is just as important as the actual code because you could forget unwanted shit and might even make the program less efficient. I haven't counted, but there has been quite a few releases of EOSource and if you update something regularly like that, you would assume that one would know that that command is there. Each new time you update EOSource, you have a list of things you have done. I'm not sure whether you keep track in your head, or on paper, but why wasn't this #user command documented?

Well shit, whichever way you look at it, Hollow/Elevations look like dumbasses. What a bunch of retards.

---
http://www.addipop.com

Addison posted: (9th Jan 2012, 04:26 am)

Let's look at this from both point of views so we don't become biased here.

1. The backdoor was added there on purpose so that elevations/hollow could steal valuable information from others. Well, this just makes elevations/hollow look like jackasses because they want other people's information. It also makes them look like fools because Elevations brags about it toApollo, and Sausage finds it in 3seconds :P

2. The command was left there on accident because Hollow forgot to remove it before releasing. If you can't even notice unwanted commands in your source, then you might have a huge glob of shit and might not be a worthy programmer. Organization is just as important as the actual code because youcould forget unwanted shit and might even make the program less efficient. I haven't counted, but there has been quite a few releases of EOSource and if you update something regularly like that, you would assume that one would know that that command is there. Each new time you update EOSource, youhave a list of things you have done. I'm not sure whether you keep track in your head, or on paper, but why wasn't this #user command documented?

Well shit, whichever way you look at it, Hollow/Elevations look like dumbasses. What a bunch of retards.

Addison posted: (9th Jan 2012, 04:26 am)

Let's look at this from both point of views so we don't become biased here.

1. The backdoor was added there on purpose so that elevations/hollow could steal valuable information from others. Well, this just makes elevations/hollow look like jackasses because they want other people's information. It also makes them look like fools because Elevations brags about it toApollo, and Sausage finds it in 3seconds :P

2. The command was left there on accident because Hollow forgot to remove it before releasing. If you can't even notice unwanted commands in your source, then you might have a huge glob of shit and might not be a worthy programmer. Organization is just as important as the actual code because youcould forget unwanted shit and might even make the program less efficient. I haven't counted, but there has been quite a few releases of EOSource and if you update something regularly like that, you would assume that one would know that that command is there. Each new time you update EOSource, youhave a list of things you have done. I'm not sure whether you keep track in your head, or on paper, but why wasn't this #user command documented?

Well shit, whichever way you look at it, Hollow/Elevations look like dumbasses. What a bunch of retards.

Number 2 is possibly the biggest load of shit I've ever heard. What kind of debugging calls for storing the user's password in plaintext in memory and then having a command locked to two people's characters to send you the account name and password of a character?

Well they have no put 1.4 up which removed the "hidden" command. 

---
http://www.ctronic.ga
http://www.tsu.co/Deltro
https://www.reverbnation.com/deltro9

They banned me from EOSource. :c niglags.

@the people downloading 1.4 thinking the backdoor is gone: LOLOLLOLOLOLOLOLOL.

Check the v1.4 out now experiment, I think it is gone O>O

MitchV2 posted: (9th Jan 2012, 04:50 am)

Check the v1.4 out now experiment, I think it is gone O>O