easyxss - Project Hosting on Google Code

Older Sep 06, 2009 r92 ([No log message]) committed by okinsey - [No log message] [No log message] Sep 06, 2009 r91 ([No log message]) committed by okinsey - [No log message] [No log message] Aug 29, 2009 r90 ([No log message]) committed by okinsey - [No log message] [No log message] Aug 09, 2009 r89 ([No log message]) committed by okinsey - [No log message] [No log message] Aug 09, 2009 r88 ([No log message]) committed by okinsey - [No log message] [No log message] Aug 08, 2009 r87 ([No log message]) committed by okinsey - [No log message] [No log message] Aug 07, 2009 r86 ([No log message]) committed by okinsey - [No log message] [No log message] Aug 07, 2009 r85 (Renamed the library to easyXDM) committed by okinsey - Renamed the library to easyXDM Renamed the library to easyXDM Aug 07, 2009 r84 ([No log message]) committed by okinsey - [No log message] [No log message] Aug 07, 2009 r83 ( Bumping version to 1.4.0 Restructured the implementa...) committed by okinsey - Bumping version to 1.4.0 Restructured the implementation of easyXSS.Interface, this now creates its own easyXSS.Channel, just like easyXSS.Channel creates its own easyXSS.Transport.ITransport. The internals of this class has also been restructured and should be easier to understand. Added the BestAvailableTransport class ++ Bumping version to 1.4.0 Restructured the implementation of easyXSS.Interface, this now creates its own easyXSS.Channel, just like easyXSS.Channel creates its own easyXSS.Transport.ITransport. The internals of this class has also been restructured and should be easier to understand. Added the BestAvailableTransport class ++ Aug 02, 2009 easyXSS-1.3.0.zip (easyXSS 1.3.0) file uploaded by okinsey - Labels: Featured Type-Archive OpSys-All Labels: Featured Type-Archive OpSys-All Aug 02, 2009 r82 (Bumped version to 1.3.0) committed by okinsey - Bumped version to 1.3.0 Bumped version to 1.3.0 Aug 01, 2009 r81 ([No log message]) committed by okinsey - [No log message] [No log message] Aug 01, 2009 easyXSS.zip (easyXSS-1.2 with working debug) file uploaded by okinsey - Labels: Featured Type-Archive OpSys-All Labels: Featured Type-Archive OpSys-All Aug 01, 2009 r80 (Added a script for packaging.) committed by okinsey - Added a script for packaging. Added a script for packaging. Aug 01, 2009 Documentation Wiki page edited by okinsey - Revision r79 Edited wiki page through web user interface. Revision r79 Edited wiki page through web user interface. Aug 01, 2009 Documentation Wiki page added by okinsey - Revision r78 Created wiki page through web user interface. Revision r78 Created wiki page through web user interface. Aug 01, 2009 easyXSS.1.2.zip (easyXSS.1.2) file uploaded by okinsey - Labels: Featured Type-Archive OpSys-All Labels: Featured Type-Archive OpSys-All Aug 01, 2009 r77 (Added headers and modified the build to include these) committed by okinsey - Added headers and modified the build to include these Added headers and modified the build to include these Jul 31, 2009 r76 ([No log message]) committed by okinsey - [No log message] [No log message] Jul 31, 2009 r75 (Added build system Restructured to be able to produce automa...) committed by okinsey - Added build system Restructured to be able to produce automatic documentation Added build system Restructured to be able to produce automatic documentation Jul 31, 2009 r74 ([No log message]) committed by okinsey - [No log message] [No log message] Jul 31, 2009 issue 3 (More reliable source of the clients domain) reported by okinsey - Today we get the clients domain from the endpoint parameter (supplied by the client). postMessage will only allow messages to and from this domain, meaning that if someone spoofs the endpoint url then no communication will happen. hashTransport uses this url for communicating so any spoofing will cause the client to not being able to read, but it will be able to write. For this reason we should also try to use document.referrer to find the domain name. Today we get the clients domain from the endpoint parameter (supplied by the client). postMessage will only allow messages to and from this domain, meaning that if someone spoofs the endpoint url then no communication will happen. hashTransport uses this url for communicating so any spoofing will cause the client to not being able to read, but it will be able to write. For this reason we should also try to use document.referrer to find the domain name. Jul 31, 2009 issue 2 (On the host side, accept a filter that decides whether to al...) reported by okinsey - To enhance security we should make it easy to set up a domain based filter. The library should accept an array of domains, or a function, that should return true if allowed. To enhance security we should make it easy to set up a domain based filter. The library should accept an array of domains, or a function, that should return true if allowed. Jul 06, 2009 r73 ([No log message]) committed by okinsey - [No log message] [No log message] Jul 05, 2009 easyxss-1.1.zip (Version 1.1) file uploaded by okinsey - Labels: Featured Type-Archive Labels: Featured Type-Archive Jul 05, 2009 r72 ([No log message]) committed by okinsey - [No log message] [No log message] Jul 05, 2009 r71 (Bumped the version to 1.1) committed by okinsey - Bumped the version to 1.1 Bumped the version to 1.1 Jul 05, 2009 r70 ([No log message]) committed by okinsey - [No log message] [No log message] Jul 04, 2009 r69 (Added support for inserting the iframe into a specified cont...) committed by okinsey - Added support for inserting the iframe into a specified container. This means that you can now have the other domain visible in the page. Added support for inserting the iframe into a specified container. This means that you can now have the other domain visible in the page. Jul 04, 2009 r68 ([No log message]) committed by okinsey - [No log message] [No log message] Jul 04, 2009 r67 ([No log message]) committed by okinsey - [No log message] [No log message] Jul 04, 2009 r66 ([No log message]) committed by okinsey - [No log message] [No log message] Jul 04, 2009 r65 (Changed the converter implementation. The JSON object can no...) committed by okinsey - Changed the converter implementation. The JSON object can now be used directly without the need of methods wrapping the call. Re-added the use of frames instead of iframes when used in a frameset. Changed the converter implementation. The JSON object can now be used directly without the need of methods wrapping the call. Re-added the use of frames instead of iframes when used in a frameset. Jul 02, 2009 issue 1 (When invoking remote methods in the clients channel-onReady ...) reported by okinsey - What steps will reproduce the problem? 1. on the client, include a call to the remote end just after the call to createInterface 2. load client using IE 8 What is the expected output? What do you see instead? An error occurs as the createInterface on the remote end has not been set up yet. Please use labels and text to provide additional information. What steps will reproduce the problem? 1. on the client, include a call to the remote end just after the call to createInterface 2. load client using IE 8 What is the expected output? What do you see instead? An error occurs as the createInterface on the remote end has not been set up yet. Please use labels and text to provide additional information. Jul 02, 2009 r64 ([No log message]) committed by okinsey - [No log message] [No log message] Jul 02, 2009 r63 ([No log message]) committed by okinsey - [No log message] [No log message] Jul 02, 2009 r62 ([No log message]) committed by okinsey - [No log message] [No log message] Jun 24, 2009 r61 ([No log message]) committed by okinsey - [No log message] [No log message] Jun 24, 2009 r60 ([No log message]) committed by okinsey - [No log message] [No log message] Jun 24, 2009 r59 ([No log message]) committed by okinsey - [No log message] [No log message] Jun 24, 2009 r57 ([No log message]) committed by okinsey - [No log message] [No log message] Jun 24, 2009 r56 ([No log message]) committed by okinsey - [No log message] [No log message] Jun 24, 2009 InterfaceDefinition Wiki page edited by okinsey Jun 24, 2009 InterfaceDefinition Wiki page edited by okinsey Jun 24, 2009 InvokingRemoteMethods Wiki page edited by okinsey Jun 24, 2009 r52 ([No log message]) committed by okinsey - [No log message] [No log message] Jun 24, 2009 InvokingRemoteMethods Wiki page edited by okinsey Jun 24, 2009 InvokingRemoteMethods Wiki page edited by okinsey Jun 24, 2009 r46 ([No log message]) committed by okinsey - [No log message] [No log message]

issue 3 (More reliable source of the clients domain) reported by okinsey - Today we get the clients domain from the endpoint parameter (supplied by the client). postMessage will only allow messages to and from this domain, meaning that if someone spoofs the endpoint url then no communication will happen. hashTransport uses this url for communicating so any spoofing will cause the client to not being able to read, but it will be able to write. For this reason we should also try to use document.referrer to find the domain name.

Today we get the clients domain from the endpoint parameter (supplied by the client). postMessage will only allow messages to and from this domain, meaning that if someone spoofs the endpoint url then no communication will happen. hashTransport uses this url for communicating so any spoofing will cause the client to not being able to read, but it will be able to write. For this reason we should also try to use document.referrer to find the domain name.

Older