Security update @ 0.10.1d menu

User Tag List

Results 1 to 3 of 3
  1. #1
    cl0wned's Avatar Corporal
    Reputation
    2
    Join Date
    Feb 2013
    Posts
    30
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Security update @ 0.10.1d

    thoughts on new patch?
    Last edited by cl0wned; 02-27-2013 at 07:41 PM.

    Security update @ 0.10.1d
  2. #2
    pushedx's Avatar Contributor
    Reputation
    259
    Join Date
    Nov 2009
    Posts
    137
    Thanks G/R
    8/137
    Trade Feedback
    0 (0%)
    Mentioned
    12 Post(s)
    Tagged
    0 Thread(s)
    Yes, the saved password implementation was seriously flawed. I wrote to them during early CBT days, but they misunderstood my point. I didn't bother trying to fight them on it. I'm glad they decided to address it finally, but it was something that should have been done a lot sooner.

    However, I've not reversed their current implementation to see if they did it correctly or not.

    How I think it should have been done is as follows::
    1. Client sends password to be saved to server
    2. Server creates pub/priv key for the IP and associates a special token for verification
    3. Server sends encrypted password hash (public key signed) to client only (not either key) which simply saves it to config file.
    4. When client logs in again, it simply sends the saved password hash (no processing).
    5. The server uses the priv key of the IP to decrypt the hash and checks against the stored token. If it matches, it's a valid password hash to be used. If it doesn't, decline using the password hash.

    The reason this would work is because the client never has either the public/private key used to encrypt/decrypt the password hash. If someone steals it or tampers with it, the server's decryption process would fail if the IP was different, and the password hash would be ignored. This is one way to help guard against password hash reply attacks, which was something you could easily do before encryption was added. After encryption was added, the same problem of someone being able to take your insecurely stored password hash was all too easy. Even though it's your fault if someone is able to grab your password hash on your computer, I still felt the implementation was flawed from a security perspective, as they forced you to store your password if you did not clear it out each time yourself manually until Open Beta.

    With my proposed method, there's still a weakness of someone being able to steal your account if they are on the same network as you, but from a security perspective, you are screwed regardless if you are saving files on your PC that someone on the network can arbitrarily take.

  3. #3
    melvone's Avatar Member
    Reputation
    1
    Join Date
    Feb 2013
    Posts
    18
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Damn i must re write my password ...

    Thx for infos

Similar Threads

  1. did feenix update their security?
    By 1kaotik1 in forum WoW EMU Questions & Requests
    Replies: 8
    Last Post: 10-23-2013, 03:11 PM
  2. "Important Security Update"
    By Gramexer in forum Diablo 3 General
    Replies: 6
    Last Post: 08-10-2012, 02:47 AM
  3. SOE Security Compromise Update
    By Confucius in forum Articles and Interviews
    Replies: 6
    Last Post: 05-13-2011, 06:54 PM
  4. Security Alert - Adobe Flash Player needs update
    By pmiller863 in forum World of Warcraft General
    Replies: 0
    Last Post: 06-03-2008, 04:28 PM
  5. New Update on the Patch!
    By Dwarpy in forum World of Warcraft General
    Replies: 1
    Last Post: 05-22-2006, 12:50 AM
All times are GMT -5. The time now is 12:48 AM. Powered by vBulletin® Version 4.2.3
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved. User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Digital Point modules: Sphinx-based search