Consider signing the connection id #1305

Closed
davidfowl opened this Issue Jan 11, 2013 · 1 comment

2 participants

@davidfowl
SignalR member

No description provided.

@davidfowl davidfowl was assigned Jan 11, 2013
@davidfowl davidfowl added a commit that referenced this issue Jan 13, 2013
@davidfowl davidfowl Signed connection ids.
- Added API to Protect/Unprotect data.
- Default implementation uses DPAPI.
- Updated tests.
- Fixed issues in .NET client where connection ids were not encoded.
- Added ASP.NET specific ProtectedData that uses the MachineKey

#1305
cc9b365
@davidfowl davidfowl added a commit that referenced this issue Jan 13, 2013
@davidfowl davidfowl Signed connection ids.
- Added API to Protect/Unprotect data.
- Default implementation uses DPAPI.
- Updated tests.
- Fixed issues in .NET client where connection ids were not encoded.
- Added ASP.NET specific ProtectedData that uses the MachineKey

#1305
08d1c3a
@davidfowl davidfowl added a commit that referenced this issue Jan 13, 2013
@davidfowl davidfowl Changed Transport.ConnectionId to be settable so that it always has t…
…he unprotected version.

- Fixed encoding of Abort request in HttpBasedTransport.

#1305
1782a90
@davidfowl davidfowl added a commit that referenced this issue Jan 13, 2013
@davidfowl davidfowl Send connection token and connection id back to client
- Connection.ConnectionId doesn't change client side.
- Updated the .NET client and JS client
- Updated the protocol version

#1305
63cd31b
@davidfowl davidfowl added a commit that referenced this issue Jan 14, 2013
@davidfowl davidfowl Made some changes per review feedback.
- Handle null connectionId after unprotect calls.
- Use singleton UTF8Encoding class.

#1305
4ceb098
@Xiaohongt
SignalR member

verified

@Xiaohongt Xiaohongt closed this Jan 14, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment