xlattice-devel Mailing List for The XLattice Project (Page 2)
Status: Beta
Brought to you by:
jddixon
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
(1) |
2005 |
Jan
(2) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
(7) |
Mar
(8) |
Apr
(11) |
May
(9) |
Jun
(5) |
Jul
(3) |
Aug
|
Sep
|
Oct
(13) |
Nov
|
Dec
|
From: Jim D. <jd...@di...> - 2006-04-11 16:21:15
|
It appears that Sourceforge CVS is lagging several weeks behind. After a recent checkout we found that, for example, protocol/stun/Client.java has a timestamp of 21:36 15-03-2006 whereas on my Linux machine it's 2006-04-05 18:34, a three week difference. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-04-05 21:41:18
|
This is the third set of XLattice protocol releases in this series. It incorporates what is as far as we know the first open source version of STUN with TLS-based authentication. As usual, there are three release: source code release as protocol-0.1.2.zip, binary as stunplus-0.1.2.zip, and stunplus-current now mirrors the binary release. The binary package should run on any machine with a recent Java run-time (1.4 or better JRE). This code has been developed and tested on Debian Linux hosts. There are several known limitations which will be documented on the Sourceforge project tracker. These will have been corrected and the code tested on Windows XP prior to the next release. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-04-03 16:51:00
|
The TLS tests now succeed after correction of an error in the test suite. However, CVS is still not working at Sourceforge. Any objections to switching to Subversion? -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: <fox...@xl...> - 2006-04-02 19:37:34
|
Starbucks Park St 10am tomorrow /fox |
From: Jim D. <jd...@di...> - 2006-03-31 09:27:45
|
Sourceforge CVS has been down for the last couple of days, so I have not been able to commit recent changes. However, TlsAcceptor is now working and passing its tests. It seems likely that TlsConnector will be working later today. The next step will be to use this code to add TLS functionality to the STUN code. It isn't clear from the RFC or any other source that I have been able to find what type of authentication STUN servers should use. We assume that STUN clients provide no dig certs and that servers can provide either self-signed or CA-signed dig certs. It is possible that they will use anonymous TLS instead, although this is subject to man-in-the-middle attacks. We will be modifying our STUN client to report on what certificates, if any, publicly accessible servers provide. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-03-28 13:56:33
|
On Tue, 28 Mar 2006, Jim Dixon wrote: > SimpleTlsClient and SimpleTlsServer now work correctly with > transport/tls/TestSimpleTls.java > in two modes: anonymous TLS and where the server has a self-signed > dig cert. The case where both client and server use self-signed > dig certs will be tested shortly. Tests now succeed after one minor bug fixed. The code is in CVS. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 |
From: Jim D. <jd...@di...> - 2006-03-28 12:36:53
|
SimpleTlsClient and SimpleTlsServer now work correctly with transport/tls/TestSimpleTls.java in two modes: anonymous TLS and where the server has a self-signed dig cert. The case where both client and server use self-signed dig certs will be tested shortly. For STUN, it is likely that anonymous TLS will do. Although it is subject to man-in-the-middle attacks, it is far more secure than what most people seem to do - leave out authentication entirely. For XLattice, TLS with both parties having self-authenticated dig certs is very likely to be standard. The next step is folding the logic in SimpleTlsClient and SimpleTlsServer back into the transport/tls codebase; after that we will add TLS to protocol/stun, what gets released as stun+. This will probably occur within the week. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 |
From: Jim D. <jd...@di...> - 2006-03-10 23:27:14
|
The second STUN+ release went out this evening. This was two releases, protocol-0.1.1.zip and stunplus-0.1.1.zip, and an update to the stunplus-current release to bring it in sync. The principal change is that both client and server now support unencrypted authentication over TCP/IP. Encrypted authentication will be supported in the next release, which should be out sometime in the next week or so. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-03-09 20:25:18
|
On Thu, 9 Mar 2006 fox...@xl... wrote: > mon 10am *bux park street? Fine with me. I'll let Mark know. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: <fox...@xl...> - 2006-03-09 08:26:08
|
mon 10am *bux park street? |
From: Jim D. <jd...@di...> - 2006-03-07 10:35:34
|
A preliminary stun+ release is in CVS and will appear in the Sourceforge files section later today. The server is running on stun.xlattice.org on ports 3480/3481. This preliminary release does not support authentication, although the machinery for this is present in the code. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-02-27 17:04:22
|
package org.xlattice.protocol.stun The STUN server is being built as running in nine threads. One is the shared secret server required by the RFC. This is currently running over bare tcpip rather than tls, but does provide usernames and passwords as specified. This has been rather thoroughly tested. Four of the servers are front-end udp binding servers. These accept BindingRequests from clients. Basic functionality has been implemented and tested. The main area of work at the moment is extended server functionality. The remaining four servers are BindingSenders, used by the BindingServers to relay responses to clients. BindingSender is complete and passes all tests. Principal remaining tasks: * extending the functionality of the BindingServer * testing the secret server with TLS connections instead of TCP * integrating these packages into a single STUN server * completing a client package -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-02-22 18:28:42
|
package org.xlattice.protocol.stun We now have working server discover in CVS, in TestSecretServer. This code locates the SRV record for STUN services in the DNS. These are attached to xlattice.org and can be retrieved using JNDI on _stun._udp.xlattice.org and _stun._tcp.xlattice.org. The code will be migrated into the STUN client shortly. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-02-20 19:11:49
|
package org.xlattice.protocol.stun We now have a working SecretServer in CVS, with a matching TestSecretServer. Testing is limited to TCP/IP transport, but XLattice transport abstractions (Acceptor, Connection, Connector) have been used, so switching to TLS will have minimal impact. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-02-08 22:17:44
|
On Sat, 4 Feb 2006, Jim Dixon wrote: > > Work has begun on experimental implementations of STUN and Kademlia. > > There is some discussion of this on the latest version of the Web site, > > under > > http://xlattice.sourceforge.net/components/protocol/ > > and very early code is now in CVS. Implementation and testing of all STUN attributes is now complete, although further refinement is likely. BindingRequest/Response/ErrorResponse messages have been tested. Work on the UDP server has begun. A TLS server will follow, but this seems likely to be complicated. Probably a Java 1.4.x server will use either JSSE or PureTLS, but a Java 1.5 server will have to use JSSE, because PureTLS doesn't appear to be compatible with 1.5. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-02-04 00:15:39
|
Early C++ code is in CVS in the cpp module. At this time the focus is on the development of a single Makefile for the whole C++ side of the project. The philosophically inclined might want to look at Peter Miller's "Recursive Make Considered Harmful" at http:// aegis.sourceforge.net/auug97.pdf -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-02-04 00:11:40
|
On Wed, 1 Feb 2006, Jim Dixon wrote: > Work has begun on experimental implementations of STUN and Kademlia. > There is some discussion of this on the latest version of the Web site, > under > http://xlattice.sourceforge.net/components/protocol/ > and very early code is now in CVS. Minor point: the Kademlia code is under http://xlattice.sourceforge.net/components/protocol/xlkad -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2006-02-01 22:15:13
|
Work has begun on experimental implementations of STUN and Kademlia. There is some discussion of this on the latest version of the Web site, under http://xlattice.sourceforge.net/components/protocol/ and very early code is now in CVS. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2005-09-22 21:39:39
|
This is a minor release of the server to correct bugs found in production use. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 |
From: Jim D. <jd...@di...> - 2005-03-11 19:59:36
|
This is a major upgrade which is now being used to support www.xlattice.org. That is, xlattice.sourceforge.net runs on Apache, but www.xlattice.org runs on CryptoServer 0.0.10. This is a caching server, meaning that once Web pages are loaded from disk they are retained in memory for an indefinite period of time. It is also a secure server: pages are loaded by content key, site build lists are digitally signed, and the master key is on a different machine several thousand miles away. Release 0.0.10 supports HTTP/0.9, HTTP/1.0, and HTTP/1.1 GET, and HTTP/1.x HEAD. It recognizes all standard headers. It is currently being tested in production use. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://jxcl.sourceforge.net Java unit test coverage http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2005-02-15 20:13:43
|
A substantially improved version of the CryptoServer. It now supports HTTP/1.1 GET and HEAD methods and has been tested with a number of domain names. Most HTTP headers are recognized. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://jxcl.sourceforge.net Java unit test coverage http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2005-02-02 20:07:16
|
This is a tarball release of a minimal server. The .zip file includes all jars necessary to run the server. Source is not included with the release, except for source for the CryptoServer itself. A rudimentary Users Guide is available here on the project Web site. In its current form, the CryptoServer software can load a Web site from disk into a cache keyed by content hash and serve that single site. This is a non-blocking HTTP/0.9 server operating from an in-memory cache. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://jxcl.sourceforge.net Java unit test coverage http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2005-01-30 18:10:52
|
CryptoServer software can now load a Web site from disk into a cache keyed by content hash and serve that single site. All of the relevant code is in CVS, including comprehensive unit tests. This is a non-blocking HTTP/0.9 server operating from an in-memory cache. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://jxcl.sourceforge.net Java unit test coverage http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2005-01-09 16:41:17
|
Much code for the CryptoServer is now in CVS. A working server is now expected by the end of January. For further information see the Roadmap at http://xlattice.sf.net/applications/httpd/roadmap.html -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://jxcl.sourceforge.net Java unit test coverage http://xlattice.sourceforge.net p2p communications infrastructure |
From: Jim D. <jd...@di...> - 2004-09-21 17:38:03
|
CoreXml's Java data binding facility has been significantly enhanced. It now is both capable of onverting an XML document to a tree of Java objects and of the reverse operation, generating an XML document from a tree of Java objects conforming to a Mapping. Documentation for all CoreXml facilities has also been considerably improved. -- Jim Dixon jd...@di... tel +44 117 982 0786 mobile +44 797 373 7881 http://jxcl.sourceforge.net Java unit test coverage http://xlattice.sourceforge.net p2p communications infrastructure |