Mailman 3 May 2013 - Twisted

[Twisted-Python] ANNOUNCING Tahoe-LAFS v1.10
by Zooko Wilcox-OHearn May 10, 2013

May 10, 2013

Folks: Tahoe-LAFS is built on Twisted and uses Twisted extensively for networking, event queue, and more. If you want to hack on a distributed storage system written in Twisted, you are welcome to join us! Here is our new Release Announcement. Regards, Zooko ------- ANNOUNCING Tahoe, the Least-Authority File System, v1.10 The Tahoe-LAFS team is pleased to announce the immediate availability of version 1.10.0 of Tahoe-LAFS, an extremely reliable distributed storage system. Get it here: … [View More]https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.rst Tahoe-LAFS is the first distributed storage system to offer "provider-independent security" — meaning that not even the operators of your storage servers can read or alter your data without your consent. Here is the one-page explanation of its unique security and fault-tolerance properties: https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/about.rst The previous stable release of Tahoe-LAFS was v1.9.2, released on July 3, 2012. v1.10.0 is a feature release which adds a new Introducer protocol, improves the appearance of the web-based user interface, improves grid security by making introducer FURLs unguessable, and fixes many bugs. See the NEWS file [1] for details. WHAT IS IT GOOD FOR? With Tahoe-LAFS, you distribute your filesystem across multiple servers, and even if some of the servers fail or are taken over by an attacker, the entire filesystem continues to work correctly, and continues to preserve your privacy and security. You can easily share specific files and directories with other people. In addition to the core storage system itself, volunteers have built other projects on top of Tahoe-LAFS and have integrated Tahoe-LAFS with existing systems, including Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django, Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and more. See the Related Projects page on the wiki [3]. We believe that strong cryptography, Free and Open Source Software, erasure coding, and principled engineering practices make Tahoe-LAFS safer than RAID, removable drive, tape, on-line backup or cloud storage. This software is developed under test-driven development, and there are no known bugs or security flaws which would compromise confidentiality or data integrity under recommended use. (For all important issues that we are currently aware of please see the known_issues.rst file [2].) COMPATIBILITY This release should be compatible with the version 1 series of Tahoe-LAFS. Clients from this release can write files and directories in the format used by clients of all versions back to v1.0 (which was released March 25, 2008). Clients from this release can read files and directories produced by clients of all versions since v1.0. Servers from this release can serve clients of all versions back to v1.0 and clients from this release can use servers of all versions back to v1.0. Except for the new optional MDMF format, we have not made any intentional compatibility changes. However we do not yet have the test infrastructure to continuously verify that all new versions are interoperable with previous versions. We intend to build such an infrastructure in the future. The new Introducer protocol added in v1.10 is backwards compatible with older clients and introducer servers, however some features will be unavailable when an older node is involved. Please see docs/nodekeys.rst [14] for details. This is the eighteenth release in the version 1 series. This series of Tahoe-LAFS will be actively supported and maintained for the foreseeable future, and future versions of Tahoe-LAFS will retain the ability to read and write files compatible with this series. LICENCE You may use this package under the GNU General Public License, version 2 or, at your option, any later version. See the file "COPYING.GPL" [4] for the terms of the GNU General Public License, version 2. You may use this package under the Transitive Grace Period Public Licence, version 1 or, at your option, any later version. (The Transitive Grace Period Public Licence has requirements similar to the GPL except that it allows you to delay for up to twelve months after you redistribute a derived work before releasing the source code of your derived work.) See the file "COPYING.TGPPL.rst" [5] for the terms of the Transitive Grace Period Public Licence, version 1. (You may choose to use this package under the terms of either licence, at your option.) INSTALLATION Tahoe-LAFS works on Linux, Mac OS X, Windows, Solaris, *BSD, and probably most other systems. Start with "docs/quickstart.rst" [6]. HACKING AND COMMUNITY Please join us on the mailing list [7]. Patches are gratefully accepted -- the RoadMap page [8] shows the next improvements that we plan to make and CREDITS [9] lists the names of people who've contributed to the project. The Dev page [10] contains resources for hackers. SPONSORSHIP Atlas Networks has contributed several hosted servers for performance testing. Thank you to Atlas Networks [11] for their generous and public-spirited support. And a special thanks to LeastAuthority [12], which employs several Tahoe-LAFS developers, for their continued support. HACK TAHOE-LAFS! If you can find a security flaw in Tahoe-LAFS which is serious enough that we feel compelled to warn our users and issue a fix, then we will award you with a customized t-shirts with your exploit printed on it and add you to the "Hack Tahoe-LAFS Hall Of Fame" [13]. ACKNOWLEDGEMENTS This is the twelfth release of Tahoe-LAFS to be created solely as a labor of love by volunteers. Thank you very much to the team of "hackers in the public interest" who make Tahoe-LAFS possible. Brian Warner on behalf of the Tahoe-LAFS team May 1, 2013 San Francisco, California, USA [1] https://tahoe-lafs.org/trac/tahoe-lafs/browser/NEWS.rst [2] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/known_issues.rst [3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects [4] https://tahoe-lafs.org/trac/tahoe-lafs/browser/COPYING.GPL [5] https://tahoe-lafs.org/trac/tahoe-lafs/browser/COPYING.TGPPL.rst [6] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/quickstart.rst [7] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev [8] https://tahoe-lafs.org/trac/tahoe-lafs/roadmap [9] https://tahoe-lafs.org/trac/tahoe-lafs/browser/CREDITS [10] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Dev [11] http://atlasnetworks.us/ [12] https://leastauthority.com/ [13] https://tahoe-lafs.org/hacktahoelafs/ [14] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/nodekeys.rst [View Less]

1 0

[Twisted-Python] Helping the Python 3 port
by Jonathan Ballet May 9, 2013

May 9, 2013

Hi, I'm interested to give a help to port Twisted to Python 3. I gave a look at the tickets on Trac tagged with py3k and those in the Python-3.x milestone. I gave a try at http://twistedmatrix.com/trac/ticket/5802 to see what still needed to be done, and after rebasing the patch on trunk and starting to hack a few modules, I noticed that I have to do those 3 things in a bunch of places: * use the newer "except Exception as e" instead of "except Exception, e" * use the print function instead … [View More]

6 12

[Twisted-Python] is it about wokkel ?
by bino＠indoakses-online.com May 7, 2013

May 7, 2013

Dear All ... I Really not sure whetehr it's about wokkel or not, please bare with me. I run a twistd tac in a tablet with Linux OS. Basically it's a wokkel based XMPP client that send a line to own XMPP server. This client also join a conference room, I monitor the conference room 1. First try, send to a bot jid and that bot didn't send any response. Result : After about 12-13 hour, : a. Conference said that the client left the room b. The system (Tablet) hang 2. Second try : send to the … [View More]

2 1

[Twisted-Python] chain certificates on the command line?
by Glyph May 6, 2013

May 6, 2013

With the recent resolution of <http://twistedmatrix.com/trac/ticket/2061>, I am wondering if there is already a plan in progress (and maybe some existing tickets) for adding intermediary chain certificate support to client and server endpoint string syntaxes? Apologies if I lost it somewhere in the somewhat lengthy discussion on that ticket :). -glyph

2 2

[Twisted-Python] Weekly Bug Summary
by exarkun＠twistedmatrix.com May 5, 2013

May 5, 2013

1 0

[Twisted-Python] suggestions for improvement in Twisted APIs
by Miika Komu May 4, 2013

May 4, 2013

Howdy, we investigated the networking APIs of Twisted (10.2) and published our findings in Ottawa Linux Symposium 2012: http://nw.dreamhosters.com/ols/ols2012/ols2012-komu.pdf We propose two types of improvements to the framework described in full detail in section 4.3.1 of the publication. First, we suggest security bug fixes. Second, we suggest improvements that can improve either the user experience (i.e. by improving latency in IPv6 environments) or developers (after all, frameworks are … [View More]

3 4

[Twisted-Python] How do I write AMP Command definitions TTD-edly?
by Laurens Van Houtven May 3, 2013

May 3, 2013

Hi, I have no issue writing AMP responders TTD-edly, they work pretty much the way any other code would. However, I did notice that the only way I'd notice if my Command definitions themselves were broken were if my functional tests start failing. It would be nice if I could write unit test driven Command specifications, as well. The quickest I could come up with was to call makeArguments/makeResponse with a few known-good/known-bad dictionaries, and see if it blows up. Is there a smarter … [View More]

4 6