The First Phantom Source Code Release is Available!

[MagnusBrading]

FINALLY (sorry for the long delay), the first Phantom source code
release is available, and it can be downloaded here:

http://www.magnusbrading.com/phantom/phantom.tar.gz

Johannes Schlumberger has done an excellent job with this first
implementation, which is complete enough for full practical testing of
the protocol core functionality! The only parts that are not fully up
to the original specs yet are some of the DHT-based Network Database
parts, but the most important core parts are already implemented also
there.

Also, performance testing shows very positive numbers, maxing out a
100 Mb/s network connection for data transfers over multi-hop Phantom
routing tunnels, so the crypto overhead does not seem to be
significant at all!

You can read a lot more about the implementation and performance
testing results in Johannes' paper here (this paper is also included
in the release package linked to above):

http://www.magnusbrading.com/phantom/phantom-implementation-paper.pdf

Finally, a big thanks to Johannes Schlumberger (and the initial work
of Michael Prinzinger) for realizing this! Now we're looking forward
to the input, testing and further development efforts of the
community!

Regards,
Magnus

[Hakuno]

It's fine :D

2011/3/5 MagnusBrading <magnus....@fortego.se>

--
You received this message because you are subscribed to the Google Groups "Phantom Protocol" group.
To post to this group, send email to phantom-...@googlegroups.com.
To unsubscribe from this group, send email to phantom-protoc...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/phantom-protocol?hl=en.

[grarpamp]

> FINALLY (sorry for the long delay), the first Phantom source code
> release is available, and it can be downloaded here:

OMG, I almost completely gave up on you guys, lol. This is awesome!
I'll play with it this weekend. Thanks for getting this seed material out :)

[Magnus Bråding]

I'm glad you didn't give up. :-) Looking forward to your
input/testing/patches.

Regards,
Magnus

[grarpamp]

> FINALLY (sorry for the long delay), the first Phantom source code
> release is available, and it can be downloaded here:

One meta question. The code has a license attached with it.
Presumably that covers just the code itself. However, the
specification does, afaict, not yet have any particular license.
And mention was made of somehow making the specification
infectious [presumably in a good way]. Therefore, until such
a time as the license of the specification has been published,
this may discourage other talented coders from coding alternative,
spec conformant, implementations. Which might in many ways
serve to limit furtherance of the protocol, not a good thing.

Has the license of the spec been decided upon, and if so,
what is it? And of course, if so, please feel free to publish
said omission alongside the spec :)

[Magnus Bråding]

There is some brief mention about some important such "specification
license clauses and restrictions" inside the white paper itself, but
nothing extensive.

Do you (or anyone else) have any ideas, suggestions or alternatives for
such licenses? As far as I know, you cannot just apply any common source
code license to a specification like this, can you?

Regards,
Magnus

[grarpamp]

> There is some brief mention about some important such "specification
> license clauses and restrictions" inside the white paper itself, but
> nothing extensive.

I need to read that part of the spec again to put what I read
and noted, and that you are referring to, into better words.

> Do you (or anyone else) have any ideas, suggestions or alternatives for
> such licenses? As far as I know, you cannot just apply any common source
> code license to a specification like this, can you?

I think it falls under the category of intellectual property.
Think for instance of the internet RFC's. There is a process
there whereby a vendor, say Cisco, can disclaim its interest
in the proprietary nature of the spec, in order to turn it
into an RFC, so people can build to it. Something like that.
ie: permission to use the spec for any use deemed fit and to
forgo all future claims as to things like patent and license
royalties on the 'paper invention'.

Perhaps think also of the IDEA and other cipher specs.

Presumably the code authors, and the university [1], employers,
etc disclaimed their interests in the code itself. So that part is
taken care of already.

[1] USA universities have developed a stronger thought that unless
you are strictly a student, (but perhaps a paid research associate,
teaching assistant, grad student on stipend, grader, staff, etc),
your projects may belong to them for future profit.

[Michael Prinzinger]

Congratulations on releasing the source code :)

I am glad the project got so far.
And I hope it will move on quickly from here!
 
All the best!

Michael

[Magnus Bråding]

Thank you Michael, both for the well-wishes and for your initial work
(both coding and recruiting-wise), without it we wouldn't be here!

Regards,
Magnus

> <mailto:phantom-...@googlegroups.com>.

> To unsubscribe from this group, send email to
> phantom-protoc...@googlegroups.com

> <mailto:phantom-protocol%2Bunsu...@googlegroups.com>.