[6/17/2013] REST Server Update

Page 1 of 2 12 LastLast
Results 1 to 15 of 21
  1. #1
    Gruntilda Gruntilda is offline
    MemberRank
    Apr 2010 Join Date
    468Posts

    [6/17/2013] REST Server Update

    bye lune
    Last edited by Gruntilda; 15-12-13 at 08:46 PM.


  2. #2
    Anotha One Wicious is online now
    MemberRank
    Jan 2013 Join Date
    StockholmLocation
    839Posts

    Re: [6/14/2013] REST Server Update

    I'm guessing you shouldn't use this if you don't have a launcher unless you want to edit your batch file every time you want to log in, since apparently you can't put False as value. Thanks for an update though.
    Last edited by Wicious; 14-06-13 at 06:02 PM.

  3. #3
    Valued Member NvrGnaStp is offline
    MemberRank
    Jan 2012 Join Date
    Escanaba, MILocation
    111Posts

    Re: [6/14/2013] REST Server Update

    Could you please explain a little bit? like what the update includes?

  4. #4
    Gruntilda Gruntilda is offline
    MemberRank
    Apr 2010 Join Date
    468Posts

    Re: [6/14/2013] REST Server Update

    Yea I just saw that it messes up with false. I'll fix that later.


    Basically, there is now the option to delete the token right after it's used. This is useful because someone brought up the this situation: Server has a file-check for their client.exe so it hasn't been modified. The exe has the shop edit button disabled to stop one of the bugs. What could happen is: you login a server normally, use process explorer to find your token, use a batch to start your own exe (that has the edit button ENABLED) to connect to the server using the token your found in process explorer, and login. If you do that within 59 seconds (default expire time of tokens), you can basically just bypass their checks, and proceed to fucking up a server.

  5. #5
    Member ChubbyCrab is offline
    MemberRank
    Jan 2012 Join Date
    95Posts

    Re: [6/14/2013] REST Server Update

    Nice bugfix. I think the EnforceDate could be deleted, it's way safer to delete used tokens instead of checking if their creation/use date is expired. Will update my guide later.

  6. #6
    Member F1ow is offline
    MemberRank
    May 2012 Join Date
    Germany/DeutschLocation
    51Posts

    Re: [6/14/2013] REST Server Update

    bug.png

    Just appearing when DeleteUserTokens is set to True...

    Working well with False...

  7. #7
    Proficient Member Canic is offline
    MemberRank
    Feb 2010 Join Date
    159Posts

    Re: [6/14/2013] REST Server Update

    Quote Originally Posted by Gruntilda View Post
    Yea I just saw that it messes up with false. I'll fix that later.


    Basically, there is now the option to delete the token right after it's used. This is useful because someone brought up the this situation: Server has a file-check for their client.exe so it hasn't been modified. The exe has the shop edit button disabled to stop one of the bugs. What could happen is: you login a server normally, use process explorer to find your token, use a batch to start your own exe (that has the edit button ENABLED) to connect to the server using the token your found in process explorer, and login. If you do that within 59 seconds (default expire time of tokens), you can basically just bypass their checks, and proceed to fucking up a server.
    Nah why you tell everyone how i could bug on every Server xD
    But anyway Thanks that to fix it after i tell you how you can bypass the check^^

  8. #8
    Account Upgraded | Title Enabled! aqua512 is offline
    MemberRank
    Nov 2012 Join Date
    574Posts

    Re: [6/14/2013] REST Server Update

    or the other option is use the rest API system from dusk/ outspark, and don't use the trash tricks files (sounds so much easier and better).
    In my opinion it would be better to have a fully functioning server (knockbacks and all) then to have some half ass work around bullshit. Oh and get your client security working. part of the xtrap system is it checks the client exe even if u were to change it out the world manager makes the server select box unclickable.


    EDIT: Why use stu's junk anyways, so he can shut all the servers down again. Haven't we learned he cannot be trusted (Launcher situation all over again).
    Last edited by aqua512; 15-06-13 at 07:51 PM.

  9. #9
    Proficient Member xWhiteCore is offline
    MemberRank
    Jun 2012 Join Date
    193Posts

    Re: [6/14/2013] REST Server Update

    @aqua512

    OdinRestServer is Clean.. there are no way to put them down..

    [6/14/2013] REST Server = also Clean.

    By the way you can write your own RestServer its very simple.

    Just grap the information and work with it.

  10. #10
    Alpha Member Cyndaquil is offline
    MemberRank
    Mar 2012 Join Date
    EnglandLocation
    2,137Posts

    Re: [6/14/2013] REST Server Update

    Quote Originally Posted by aqua512 View Post
    or the other option is use the rest API system from dusk/ outspark, and don't use the trash tricks files (sounds so much easier and better).
    In my opinion it would be better to have a fully functioning server (knockbacks and all) then to have some half ass work around bullshit. Oh and get your client security working. part of the xtrap system is it checks the client exe even if u were to change it out the world manager makes the server select box unclickable.


    EDIT: Why use stu's junk anyways, so he can shut all the servers down again. Haven't we learned he cannot be trusted (Launcher situation all over again).
    Lol how is Stu gunna shutdown servers with a service... He isn't now stop starting drama where it isn't needed. If he wanted to shut down servers; he wouldn't have released the fix for people so that others don't ruin servers. Now think before you speak scum.

  11. #11
    ExtrinsicStudioâ„¢ Myth is offline
    MemberRank
    Jan 2012 Join Date
    367Posts

    Re: [6/14/2013] REST Server Update


  12. #12
    Novice Zancrow is offline
    MemberRank
    Jun 2013 Join Date
    3Posts

    Re: [6/14/2013] REST Server Update

    Quote Originally Posted by Gruntilda View Post
    You'll have to add a new setting in the the SHN. Read Main.txt.
    Can anyone tell me what new setting?

    Quote: Invalid value [OdinServer.TokenManager.EnforceExpireDate]::<SETTING NOT FOUND>
    Is added in my .shn with value true. But it doesn't work.

  13. #13
    Electro, dude. Bakey is offline
    MemberRank
    Oct 2010 Join Date
    403Posts

    Re: [6/14/2013] REST Server Update

    This is all a hack, guys. Stu is trying to steal all of your nudes, and professional scripts.

  14. #14
    Valued Member NvrGnaStp is offline
    MemberRank
    Jan 2012 Join Date
    Escanaba, MILocation
    111Posts

    Re: [6/14/2013] REST Server Update

    Quote Originally Posted by Bakey View Post
    This is all a hack, guys. Stu is trying to steal all of your nudes, and professional scripts.
    Sounds legit, Probably deletes your system32 and SysWOW64 after finding and uploading those nudes.

  15. #15
    Gruntilda Gruntilda is offline
    MemberRank
    Apr 2010 Join Date
    468Posts

    Re: [6/14/2013] REST Server Update

    Updated again. Fixed the weird True/False not working or whatever. Same link.



Page 1 of 2 12 LastLast

Advertisement