- cypherpunks-legacy - lists.cpunks.org

map of tor routers
by Bryan Fordham 06 Jul '18

06 Jul '18

I've taken up the task creating a map of tor routers. I have a test image up at [1]http://socialistsushi.com/tor.png So far I have a mapserver and data on tor routers in a postgis database, so I can produce images like the one above. Now that I've figured that out, I'd like some comments on how I plan to proceed. Basically, my idea at this point is to query a directory server once a day, and check for running nodes. I'll add new nodes as they appear, and mark ones that are no longer running. I plan to also track if they are stable, and an exit node. This way I'll be able to produce maps showing all nodes, all running exit nodes, and other combinations. Is there a better way of tracking routers? What else should I track? Other comments? I'm not using google maps so I can keep javascript out. I'm using UMN MapServer ([2]http://mapserver.gis.umn.edu/) for those who are interested in such things. I may do a nicer UI (javascript-enabled) for those who aren't worried about such things. Thanks --B References 1. http://socialistsushi.com/tor.png 2. http://mapserver.gis.umn.edu/ ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]

1 0

27C3 on Tor
by Eugen Leitl 06 Jul '18

06 Jul '18

(via arsetechnica) http://arstechnica.com/tech-policy/news/2010/12/flaws-in-tor-anonymity-netw… Flaws in Tor anonymity network spotlighted By John Borland, wired.com | Last updated about 4 hours ago At the Chaos Computer Club Congress in Berlin, Germany on Monday, researchers from the University of Regensburg delivered a new warning about the Tor anonymizer network, a system aimed at hiding details of a computer userbs online activity from spying eyes. The attack doesnbt quite make a surferbs activity an open book, but offers the ability for someone on the same local networkba Wi-Fi network provider, or an ISP working at law enforcement (or a regimebs) request, for examplebto gain a potentially good idea of sites an anonymous surfer is viewing. b Developers have to be aware of this kind of attack, and develop countermeasures,b said Dominik Herrmann, a Regensburg PhD student studying profiling and fingerprinting attacks. b But that proves to be very difficult.b The research, performed by a variety of collaborators in Germany working on anonymity measures, represents a warning for privacy-conscious users wary of spying eyes, whether behind Net-unfriendly borders or simply corporate firewalls. Tor is essentially an online mask, rather than a tool that hides the fact or content of communication itself. The projectbs developers are addressing the problem of traffic analysisbessentially the threat that an attacker or observer might be able to tease out a personbs identity, location, profession, social network or other information about the message content by analyzing a messagebs unencrypted headers. To hide this information, the Tor system routes messages around a winding path of volunteer servers across the Net, with each relay point knowing only the address of the previous and next step in the pathway. Once this circuit has been established, neither an eavesdropper nor a compromised relay will theoretically have the ability to determine both the source and destination of a given piece of communication. According to the Tor projectbs latest metrics, the network has drawn between 100,000 and 300,000 users per day over the last several months. Herrmann and his fellow researchers say therebs a partial flaw in this arrangement, however. A potential eavesdropper on the end userbs own network still has the ability to analyze the patterns of data being returned, and in many cases will be able to develop a reasonable guess about the source of the communication. An attackerbperhaps an ISP instructed by law enforcement or a government to engage in such surveillancebwould first have to develop a list of potential sites that the target might be visiting, or that it was interested in monitoring. It would then run the Tor system itself, testing the way these sites appeared when accessed through Tor, developing a database of b fingerprintsb associated with the sites of interest. Once the target of the surveillance went online, the eavesdropper would capture the packet stream as it crossed the local network and compare the source data with its fingerprint database with the help of pattern recognition software. Any match would be only statistical, giving somewhere between 55 percent and 60 percent certainty, Herrmann saidbnot enough to provide hard evidence in court, but likely more certainty than many people seeking privacy might be comfortable with. Different online destinations will carry different susceptibility to fingerprinting, of course. Unusual sites, with characteristics such as very heavy or large graphic use, can be more easily identified, Herrmann said. By the same token, the easiest way for a website to fool such an eavesdropper would be to make its site look as closely as possible like another popular sitebmimicking the look of the Google site, for example, one of the most commonly accessed pages on the Web. Users themselves can guard against this type of fingerprint-based eavesdropping relatively easily, Herrmann noted. Downloading or requesting more than one site at a time through the network will muddy the pattern enough that certainty will be very difficult for the eavesdropper to establish. The research many not dissuade many from using Tor, which remains one of the most promising approaches for individuals seeking to hide aspects of their identity or online activity. But it may well make them work harder. ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE

1 0

27C3 on Tor
by Eugen Leitl 06 Jul '18

06 Jul '18

(via arsetechnica) http://arstechnica.com/tech-policy/news/2010/12/flaws-in-tor-anonymity-netw… Flaws in Tor anonymity network spotlighted By John Borland, wired.com | Last updated about 4 hours ago At the Chaos Computer Club Congress in Berlin, Germany on Monday, researchers from the University of Regensburg delivered a new warning about the Tor anonymizer network, a system aimed at hiding details of a computer userbs online activity from spying eyes. The attack doesnbt quite make a surferbs activity an open book, but offers the ability for someone on the same local networkba Wi-Fi network provider, or an ISP working at law enforcement (or a regimebs) request, for examplebto gain a potentially good idea of sites an anonymous surfer is viewing. b Developers have to be aware of this kind of attack, and develop countermeasures,b said Dominik Herrmann, a Regensburg PhD student studying profiling and fingerprinting attacks. b But that proves to be very difficult.b The research, performed by a variety of collaborators in Germany working on anonymity measures, represents a warning for privacy-conscious users wary of spying eyes, whether behind Net-unfriendly borders or simply corporate firewalls. Tor is essentially an online mask, rather than a tool that hides the fact or content of communication itself. The projectbs developers are addressing the problem of traffic analysisbessentially the threat that an attacker or observer might be able to tease out a personbs identity, location, profession, social network or other information about the message content by analyzing a messagebs unencrypted headers. To hide this information, the Tor system routes messages around a winding path of volunteer servers across the Net, with each relay point knowing only the address of the previous and next step in the pathway. Once this circuit has been established, neither an eavesdropper nor a compromised relay will theoretically have the ability to determine both the source and destination of a given piece of communication. According to the Tor projectbs latest metrics, the network has drawn between 100,000 and 300,000 users per day over the last several months. Herrmann and his fellow researchers say therebs a partial flaw in this arrangement, however. A potential eavesdropper on the end userbs own network still has the ability to analyze the patterns of data being returned, and in many cases will be able to develop a reasonable guess about the source of the communication. An attackerbperhaps an ISP instructed by law enforcement or a government to engage in such surveillancebwould first have to develop a list of potential sites that the target might be visiting, or that it was interested in monitoring. It would then run the Tor system itself, testing the way these sites appeared when accessed through Tor, developing a database of b fingerprintsb associated with the sites of interest. Once the target of the surveillance went online, the eavesdropper would capture the packet stream as it crossed the local network and compare the source data with its fingerprint database with the help of pattern recognition software. Any match would be only statistical, giving somewhere between 55 percent and 60 percent certainty, Herrmann saidbnot enough to provide hard evidence in court, but likely more certainty than many people seeking privacy might be comfortable with. Different online destinations will carry different susceptibility to fingerprinting, of course. Unusual sites, with characteristics such as very heavy or large graphic use, can be more easily identified, Herrmann said. By the same token, the easiest way for a website to fool such an eavesdropper would be to make its site look as closely as possible like another popular sitebmimicking the look of the Google site, for example, one of the most commonly accessed pages on the Web. Users themselves can guard against this type of fingerprint-based eavesdropping relatively easily, Herrmann noted. Downloading or requesting more than one site at a time through the network will muddy the pattern enough that certainty will be very difficult for the eavesdropper to establish. The research many not dissuade many from using Tor, which remains one of the most promising approaches for individuals seeking to hide aspects of their identity or online activity. But it may well make them work harder. ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE

1 0

[tahoe-lafs-weekly-news] TWN 13
by Patrick R McDonald 06 Jul '18

06 Jul '18

=========================================================== Tahoe-LAFS Weekly News, issue number 13, September 6, 2011 =========================================================== Welcome to the Tahoe-LAFS Weekly News (TWN). Tahoe-LAFS_ is a secure, distributed storage system. `View TWN on the web`_ *or* `subscribe to TWN`_. .. _Tahoe-LAFS: http://tahoe-lafs.org .. _View TWN on the web: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/TahoeLAFSWeeklyNews .. _subscribe to TWN: http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news Announcements and News ====================== Brian provided another `status update`_ on 1.9. Work continues apace on MDMF. Some bugs forced the developers to restructure some of the MDMF code resulting in the current delay. Look for alpha2 this weekend. A couple weeks after alpha2 should be code freeze and the release of beta1. While no hard deadline is set, it appears 1.9 will see release in early October. Raddi from NoiseBridge_ notified that their Tahoe-LAFS grid is coming along. You may remember NoiseBridge from the first Tahoe-LAFS summit. Thanks again to NoiseBridge for providing us the space. .. _status update: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-September/006671.html .. _NoiseBridge: https://noisebridge.net/wiki/Noisebridge >From the tahoe-dev Mailing List =============================== Vlastimil posted a wonderful HOWTO on using `Tahoe-LAFS with pyfilesystem and Dokan`_. This HOWTO is also posted on the `Tips and Tricks page`_. Renat posted a question on what to do when `adding new nodes` to a Tahoe grid. Zooko pointed him to the "repair" function. To access the "repair" function, in the WUI, click the repair button, in the CLI, run either "tahoe check" or "tahoe deepcheck". Ticket #643_ covers automatically scheduling the repair process. It even includes a link to `Kevin Reid's cron script` which does it automatically. Lastly, Renat provide the statistics from his Suse Gallery Live CD of Tahoe. "6 builds, 1.5 GB - 32-bit x86 - edited 10 days ago 2 releases, 77 downloads, 3 clones, 3 comments" [1_] Great to see the Live CD is getting good feedback. .. _Tahoe-LAFS with pyfilesystem and Dokan: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-August/006663.html .. _Tips and Tricks page: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/TipsTricks .. _adding new nodes: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-September/006670.html .. _643: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/643 .. _Kevin Reid's cron script: http://tahoe-lafs.org/pipermail/tahoe-dev/2009-October/003012.html .. _1: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-September/006673.html Patches Needing Review of the Week ================================== There are three (3) tickets still needing review for 1.9: * 393_: MDMF * 1398_: make docs/performance.rst more precise and accurate * 1506_: mutable-type should imply mutable in tahoe put Let's see if we can't get these reviewed and 1.9 out the door. .. _393: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/393 .. _1398: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1398 .. _1506: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1506 Open Source Project of the Week =============================== The Open Source project of the week is AllMyData's `iPhone client`_. .. _iPhone client: http://tahoe-lafs.org/trac/tahoe-iphone-client ---- *The Tahoe-LAFS Weekly News is published once a week by The Tahoe-LAFS Software Foundation, President and Treasurer: Peter Secor. Scribes: Patrick "marlowe" McDonald, Zooko Wilcox-O'Hearn, Editor: Zooko.* `View TWN on the web`_ *or* `subscribe to TWN`_ *. Send your news stories to* marlowe(a)antagonism.org_ *b submission deadline: Friday night.* .. _marlowe(a)antagonism.org: mailto:marlowe@antagonism.org .. |zooko| image:: http://secorp.net/images/zooko.png :height: 35 :alt: zooko :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |brian| image:: http://secorp.net/images/warner.png :height: 35 :alt: brian :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |davidsarah| image:: http://secorp.net/images/davidsarah_bw.png :height: 35 :alt: davidsarah :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |kevan| image:: http://secorp.net/images/kevan_c_bw_sm.png :height: 35 :alt: kevan :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |peter| image:: http://secorp.net/images/psecor.jpg :height: 35 :alt: peter :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |marlowe| image:: http://tahoe-lafs.org/trac/tahoe-lafs/raw-attachment/wiki/AboutUs/marlowe-x… :height: 35 :alt: marlowe :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |franC'ois| image:: http://tahoe-lafs.org/trac/tahoe-lafs/raw-attachment/wiki/AboutUs/francois_… :height: 35 :alt: franC'ois :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |frC)dC)ric| image:: http://tahoe-lafs.org/trac/tahoe-lafs/raw-attachment/wiki/AboutUs/freestorm… :height: 35 :alt: frC)dC)ric :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |marc| image:: http://secorp.net/images/midnight_magic_sm.jpg :height: 35 :alt: marc :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs -- ---------------------------------------------------------------- | Patrick R. McDonald GPG Key: 668AA5DF | | https://www.antagonism.org/ <marlowe(a)antagonism.org> | | <mcdonald.patrick.r(a)gmail.com> | | <patrick(a)opensecurityfoundation.org> | ---------------------------------------------------------------- | Malo periculosam libertatem quam quietum servitium | ---------------------------------------------------------------- _______________________________________________ tahoe-lafs-weekly-news mailing list tahoe-lafs-weekly-news(a)tahoe-lafs.org http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE

1 0

Lucrative update
by Patrick 06 Jul '18

06 Jul '18

Lucrative release 4 is out. I know many people are used to seeing releases numbered like "0.000001", "0.000002", "2.0.3.0.14.657" etc. but release numbering systems are essentially arbitrary in nature so don't get excited as Lucrative goes toward version 50+. This release is a fairly minor one, but included some changes such as the client name that I wanted to get out as soon as possible. There is also a new development weblog at http://lucrative.thirdhost.com/weblog/. I went through an install with someone over IRC last night and made a blog entry summarizing the install notes. I recommend reading the notes before attempting an install. I am glad to help with an install, drop me a note at patrick(a)lfcgate.com if you have trouble. Some documentation on the various entities in the Lucrative system is now available on the website, http://lucrative.thirdhost.com/documentation.php but more is needed and coming. If Lucrative is interesting to you, please consider helping in any way you can: Feedback Installation reports Suggestions Comments Criticism Feature requests Source code patches Donations Are all very much welcomed. And criticism is more useful to me than praise. My sincere thanks to everyone who has participated so far by installing, testing, providing feedback, spreading the word, and donating. And finally I just received word from SourceForge that the project registration for Lucrative has been approved. Regards, Patrick -----BEGIN PGP PUBLIC KEY BLOCK----- Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com> mQGiBD5ECKcRBADUvjXHwLtxIyS4AyjBs/dFtN6rdeP18Fhzh1hD5fJwkFevqY9Z I1ASROTh6eXYF7pU5sEvbcPshHyTB41ZtTqZvQvpwWN0fUzOuutuI0mtC5UPp9Rz j47SdWLdEXNHjwnHDCYSyqtqZu8GujGRQybR0eP3NIh/NwbSDUKdgz7IjwCg//Jo UtjP3zUFobm/0UYA+CJ5krED/091x9Js0gwNwvjbzM8DqO+r8qNz0kXI13FkrPRk QNd37lxt6m2m8HZD1WYM2wKwtMzHSwJcWzaDZ/tNc+ppYjzpw0EQCh9FqjGs8Vau guF6PA1M8lJTCcLKaL4e7ynic+PAw5Xa/tdOYgFCG+eLMU5RLvzRCYoOLIjgMJLJ yG98BACAMlDmFVYgC/UKvzZmHfZ5CtCKd8sPfCXrYLu5NeFRE0LR6D6zjzmhi1xX okfreR5o3T/y78VBM98js+m2/+7Z0AElqydeW/RnV1zqwDGjDr9z2MgARf3yLAbs n3BU8Fz61RwvHy6cRkT+2dR2f69QQUSpkupvLwZIGX/iwm4uKLQdUGF0cmljayA8 cGF0cmlja0BsZmNnYXRlLmNvbT6JAE4EEBECAA4FAj5ECKcECwMCAQIZAQAKCRBb mvb9yuOVfaA2AKDAu5tDj9F2KI8cJMrKKkQRAcUyxACg6/bei7lUJH+E5igJqGRx SjKrRA65BA0EPkQIpxAQAPkYoH5aBmF6Q5CV3AVsh4bsYezNRR8O2OCjecbJ3HoL rOQ/40aUtjBKU9d8AhZIgLUV5SmZqZ8HdNP/46HFliBOmGW42A3uEF2rthccUdhQ yiJXQym+lehWKzh4XAvb+ExN1eOqRsz7zhfoKp0UYeOEqU/Rg4Soebbvj6dDRgjG zB13VyQ4SuLE8OiOE2eXTpITYfbb6yUOF/32mPfIfHmwch04dfv2wXPEgxEmK0Ng w+Po1gr9oSgmC66prrNlD6IAUwGgfNaroxIe+g8qzh90hE/K8xfzpEDp19J3tkIt AjbBJstoXp18mAkKjX4t7eRdefXUkk+bGI78KqdLfDL2Qle3CH8IF3KiutapQvMF 6PlTETlPtvFuuUs4INoBp1ajFOmPQFXz0AfGy0OplK33TGSGSfgMg71l6RfUodNQ +PVZX9x2Uk89PY3bzpnhV5JZzf24rnRPxfx2vIPFRzBhznzJZv8V+bv9kV7HAarT W56NoKVyOtQa8L9GAFgr5fSI/VhOSdvNILSd5JEHNmszbDgNRR0PfIizHHxbLY72 88kjwEPwpVsYjY67VYy4XTjTNP18F1dDox0YbN4zISy1Kv884bEpQBgRjXyEpwpy 1obEAxnIByl6ypUM2Zafq9AKUJsCRtMIPWakXUGfnHy9iUsiGSa6q6Jew1XrPdYX AAICD/wKwtF7Y4NKBe8PQ6jDbjWziiTv9Ac/EnRTJDQEoqgLa2LyE+6Ahw/VPGvp mfxkD2MKxC9E7kYVmasn6sHnSpvAv3e7O1Bqbo/qLzzCcJQ5VCurZ+elRM1GZ4Oc fM19FPKutb0/JFEv0nrqS4BGkF7WFBbu5dKYl/GIO7Co1mAerFIb719dOwMPVEIz OT08u8uB9jyR8gEElf+CVuNfOUkrUGg4HS4SbmTTrCSz3/8n5PkquSuAyjCB/dwM ZsZwA0/TTR8sDYlmlf9xPj5PGpGnV9OUwfig6eE0eWtRFeasmz0uiX+yp45ABtNh 6EXP/PFaBgXi9omXXjeeFYfpDvmfA6izvTIQfXTV6V9ZWrBfXarM+GQ+6guXWVbd 9fXvmCr982LkzuKQrK1OpRXBMUapXL+tOy/LYzz91InqKKhgPNGa12fvotZ4LzlM iqoM+Hpz5L9B5We1Ph0lD6RBVXDCqd+P8extnY/7AaDy7tC0UghaAaUuEZXJQPIc oQ3QGbpjM0nGe/VZN5EZhljau0NNENFaU56cOpvOhcO04gLGNNc2NS+rIpTMsaHh o1CG90c5zZZJuUbyx0mIHriNQXDgEwunSZPQorKK9KSppyyjeuOyi5F/mBBPXeyT weLhLqLvAr9se/+Z3aQvMADJi8zUZtGggLTw+N9R5XSwtSh2R4kARgQYEQIABgUC PkQIpwAKCRBbmvb9yuOVfWayAKC+mBhHdn1XZ5uH0RocAyJ32hx2kgCePyhB+IqM TjWLDLarQxcPYhbkFi4= =nx1M -----END PGP PUBLIC KEY BLOCK----- --- end forwarded text -- ----------------- R. A. Hettinga <mailto: rah(a)ibuc.com> The Internet Bearer Underwriting Corporation <http://www.ibuc.com/> 44 Farquhar Street, Boston, MA 02131 USA "... however it may deserve respect for its usefulness and antiquity, [predicting the end of the world] has not been found agreeable to experience." -- Edward Gibbon, 'Decline and Fall of the Roman Empire' --------------------------------------------------------------------- The Cryptography Mailing List Unsubscribe by sending "unsubscribe cryptography" to majordomo(a)wasabisystems.com

1 0

map of tor routers
by Bryan Fordham 06 Jul '18

06 Jul '18

I've taken up the task creating a map of tor routers. I have a test image up at [1]http://socialistsushi.com/tor.png So far I have a mapserver and data on tor routers in a postgis database, so I can produce images like the one above. Now that I've figured that out, I'd like some comments on how I plan to proceed. Basically, my idea at this point is to query a directory server once a day, and check for running nodes. I'll add new nodes as they appear, and mark ones that are no longer running. I plan to also track if they are stable, and an exit node. This way I'll be able to produce maps showing all nodes, all running exit nodes, and other combinations. Is there a better way of tracking routers? What else should I track? Other comments? I'm not using google maps so I can keep javascript out. I'm using UMN MapServer ([2]http://mapserver.gis.umn.edu/) for those who are interested in such things. I may do a nicer UI (javascript-enabled) for those who aren't worried about such things. Thanks --B References 1. http://socialistsushi.com/tor.png 2. http://mapserver.gis.umn.edu/ ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]

1 0

[tahoe-lafs-weekly-news] TWN 13
by Patrick R McDonald 06 Jul '18

06 Jul '18

=========================================================== Tahoe-LAFS Weekly News, issue number 13, September 6, 2011 =========================================================== Welcome to the Tahoe-LAFS Weekly News (TWN). Tahoe-LAFS_ is a secure, distributed storage system. `View TWN on the web`_ *or* `subscribe to TWN`_. .. _Tahoe-LAFS: http://tahoe-lafs.org .. _View TWN on the web: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/TahoeLAFSWeeklyNews .. _subscribe to TWN: http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news Announcements and News ====================== Brian provided another `status update`_ on 1.9. Work continues apace on MDMF. Some bugs forced the developers to restructure some of the MDMF code resulting in the current delay. Look for alpha2 this weekend. A couple weeks after alpha2 should be code freeze and the release of beta1. While no hard deadline is set, it appears 1.9 will see release in early October. Raddi from NoiseBridge_ notified that their Tahoe-LAFS grid is coming along. You may remember NoiseBridge from the first Tahoe-LAFS summit. Thanks again to NoiseBridge for providing us the space. .. _status update: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-September/006671.html .. _NoiseBridge: https://noisebridge.net/wiki/Noisebridge >From the tahoe-dev Mailing List =============================== Vlastimil posted a wonderful HOWTO on using `Tahoe-LAFS with pyfilesystem and Dokan`_. This HOWTO is also posted on the `Tips and Tricks page`_. Renat posted a question on what to do when `adding new nodes` to a Tahoe grid. Zooko pointed him to the "repair" function. To access the "repair" function, in the WUI, click the repair button, in the CLI, run either "tahoe check" or "tahoe deepcheck". Ticket #643_ covers automatically scheduling the repair process. It even includes a link to `Kevin Reid's cron script` which does it automatically. Lastly, Renat provide the statistics from his Suse Gallery Live CD of Tahoe. "6 builds, 1.5 GB - 32-bit x86 - edited 10 days ago 2 releases, 77 downloads, 3 clones, 3 comments" [1_] Great to see the Live CD is getting good feedback. .. _Tahoe-LAFS with pyfilesystem and Dokan: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-August/006663.html .. _Tips and Tricks page: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/TipsTricks .. _adding new nodes: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-September/006670.html .. _643: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/643 .. _Kevin Reid's cron script: http://tahoe-lafs.org/pipermail/tahoe-dev/2009-October/003012.html .. _1: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-September/006673.html Patches Needing Review of the Week ================================== There are three (3) tickets still needing review for 1.9: * 393_: MDMF * 1398_: make docs/performance.rst more precise and accurate * 1506_: mutable-type should imply mutable in tahoe put Let's see if we can't get these reviewed and 1.9 out the door. .. _393: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/393 .. _1398: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1398 .. _1506: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1506 Open Source Project of the Week =============================== The Open Source project of the week is AllMyData's `iPhone client`_. .. _iPhone client: http://tahoe-lafs.org/trac/tahoe-iphone-client ---- *The Tahoe-LAFS Weekly News is published once a week by The Tahoe-LAFS Software Foundation, President and Treasurer: Peter Secor. Scribes: Patrick "marlowe" McDonald, Zooko Wilcox-O'Hearn, Editor: Zooko.* `View TWN on the web`_ *or* `subscribe to TWN`_ *. Send your news stories to* marlowe(a)antagonism.org_ *b submission deadline: Friday night.* .. _marlowe(a)antagonism.org: mailto:marlowe@antagonism.org .. |zooko| image:: http://secorp.net/images/zooko.png :height: 35 :alt: zooko :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |brian| image:: http://secorp.net/images/warner.png :height: 35 :alt: brian :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |davidsarah| image:: http://secorp.net/images/davidsarah_bw.png :height: 35 :alt: davidsarah :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |kevan| image:: http://secorp.net/images/kevan_c_bw_sm.png :height: 35 :alt: kevan :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |peter| image:: http://secorp.net/images/psecor.jpg :height: 35 :alt: peter :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |marlowe| image:: http://tahoe-lafs.org/trac/tahoe-lafs/raw-attachment/wiki/AboutUs/marlowe-x… :height: 35 :alt: marlowe :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |franC'ois| image:: http://tahoe-lafs.org/trac/tahoe-lafs/raw-attachment/wiki/AboutUs/francois_… :height: 35 :alt: franC'ois :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |frC)dC)ric| image:: http://tahoe-lafs.org/trac/tahoe-lafs/raw-attachment/wiki/AboutUs/freestorm… :height: 35 :alt: frC)dC)ric :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |marc| image:: http://secorp.net/images/midnight_magic_sm.jpg :height: 35 :alt: marc :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs -- ---------------------------------------------------------------- | Patrick R. McDonald GPG Key: 668AA5DF | | https://www.antagonism.org/ <marlowe(a)antagonism.org> | | <mcdonald.patrick.r(a)gmail.com> | | <patrick(a)opensecurityfoundation.org> | ---------------------------------------------------------------- | Malo periculosam libertatem quam quietum servitium | ---------------------------------------------------------------- _______________________________________________ tahoe-lafs-weekly-news mailing list tahoe-lafs-weekly-news(a)tahoe-lafs.org http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE

1 0

None
by Nathan Saper 06 Jul '18

06 Jul '18

> The reason why I use "the least pain for the greatest number" instead of > "the greatest happiness for the greatest number" is because the latter > justifies many not-so-great acts under act utilitarianism. Killing someone brings the amount of future pain he's gonna suffer to zero. That implies that - according to your ideas - one is morally justified in killing anyone and everyone (as painless as possible, but that's not an important point, as long as it's less than the total amount of pain that person would suffer for the rest of his life). I'd say that using happiness is a little better :) Another problem with utilitarianism is that it requires one to be able to evaluate - or at least compare - happiness (or pain), something which is impossible (subjectivism and all). [See Walter Block's utilitarian demonstration that O.J.Simpson was morally justified to kill his wife.] Not to mention that your stupidity is giving me a headache... Mark

1 0

None
by Nathan Saper 06 Jul '18

06 Jul '18

> The reason why I use "the least pain for the greatest number" instead of > "the greatest happiness for the greatest number" is because the latter > justifies many not-so-great acts under act utilitarianism. Killing someone brings the amount of future pain he's gonna suffer to zero. That implies that - according to your ideas - one is morally justified in killing anyone and everyone (as painless as possible, but that's not an important point, as long as it's less than the total amount of pain that person would suffer for the rest of his life). I'd say that using happiness is a little better :) Another problem with utilitarianism is that it requires one to be able to evaluate - or at least compare - happiness (or pain), something which is impossible (subjectivism and all). [See Walter Block's utilitarian demonstration that O.J.Simpson was morally justified to kill his wife.] Not to mention that your stupidity is giving me a headache... Mark

1 0

None
by Nathan Saper 06 Jul '18

06 Jul '18

> The reason why I use "the least pain for the greatest number" instead of > "the greatest happiness for the greatest number" is because the latter > justifies many not-so-great acts under act utilitarianism. Killing someone brings the amount of future pain he's gonna suffer to zero. That implies that - according to your ideas - one is morally justified in killing anyone and everyone (as painless as possible, but that's not an important point, as long as it's less than the total amount of pain that person would suffer for the rest of his life). I'd say that using happiness is a little better :) Another problem with utilitarianism is that it requires one to be able to evaluate - or at least compare - happiness (or pain), something which is impossible (subjectivism and all). [See Walter Block's utilitarian demonstration that O.J.Simpson was morally justified to kill his wife.] Not to mention that your stupidity is giving me a headache... Mark

1 0