uLobby 1.2.3 now available

42 views
Skip to first unread message

Lars Liljenberg

unread,
Jan 19, 2014, 5:07:54 PM1/19/14
to UnityPark Suite Announcements
Dear UnityPark developers,

uLobby has just received a maintenance update that fixes some important security issues and adds some small improvements. Note that due to some necessary internal changes, 1.2.3 is not network compatible with 1.2.2 or older. This means that game clients and servers running 1.2.2 cannot connect to a lobby server running 1.2.3, and vice versa.

We highly recommend updating to this newer version, which you can find on our download page. Happy coding!

uLobby 1.2.3 Werecat (2014-01-17)

Fixes:
  • Fixed issue that could cause multiple users to log in to the same user account if the login attempts were made in rapid succession.
  • Fixed possible DoS vulnerabilites that would be caused by sending specially crafted bad packets.
  • Fixed handling of encrypted messages received in the lobby server while disabling security for a peer.
Improvements:
  • Added authorative closing of peer connections using the Lobby.CloseConnection method.
  • Optimized low level message parsing and handling.
  • Added informative warning messages when attempting to uninitialize security for connections whose security is in the process of being initialized.
  • Added informative exception when attempting to initialize or uninitialize security for the lobby peer.
Changes:
  • When attempting to log in to an account, the password will now always be verified before checking whether the user is already online. If the user is already online but the password was wrong, the operation will fail with the AccountError.InvalidPassword error instead of AccountError.AlreadyLoggedIn.
  • Lobby.IsPeerConnected now returns true when called with the lobby peer as argument.
  • uLobby 1.2.3 is NOT network compatible with uLobby 1.2.2 or older, because of fixes in the connection handshake protocol. This means a game client or game server running 1.2.3 can only connect to a lobby server running 1.2.3, and vice versa.

Sincerely,

Lars Liljenberg
Reply all
Reply to author
Forward
0 new messages