July 2018 - cypherpunks-legacy

[Politech] Computers Freedom and Privacy conference in Seattle from Apr 12-15 [priv]
by Declan McCullagh 06 Jul '18

06 Jul '18

[Any Politechnicals going? I'm teaching a graduate public policy course this semester -- the last class meets on April 16, so I'm not sure if I'm going to be able to make it to Seattle. It would have to be a quick trip, at least for me. --Declan] -------- Original Message -------- Subject: CFP - post to politech list? Date: Wed, 16 Mar 2005 14:09:40 -0800 From: Deborah Pierce <dsp(a)privacyactivism.org> To: declan(a)well.com Hi Declan, Would you post this to your list. I'd like to remind everyone to book early for the conference while we still have the good rates and discounts! I've also highlighted a few of the panels that will take place at this year's conference. Thanks, Deborah Pierce PrivacyActivism Chair, CFP2005 A _detailed program_ for the 15th annual ACM Conference on Computers, Freedom, and Privacy is available on the _CFP2005 website_. CFP2005 will be held at the Westin Hotel in Seattle, WA, April 12-15, 2005. Discounted registration, and special conference rates at the Seattle Westin remain available through March 21, register before that date in order to get the advance discounts. This year's theme is _Panopticon_: Over time, and particularly recently, surveillance of ordinary citizens has increased to dramatic levels. Not only are governments watching more aspects of their citizens' lives, but those in the private sector are increasing surveillance of people as well. Often lost in the race to "increase intelligence" are discussions about different approaches to address problems like the threat of terrorism that are equally or more effective, but do not involve extensive and constant surveillance. The opening plenary debate focuses on "Sousveillance in the Panopticon?. Panel members include _Dr. Steve Mann_, Director of the eyeTap Personal Imaging Lab at the University of Toronto, known for his work in wearable cameras and computing; _Dr. Latanya Sweeney_, Director of the _Data Privacy Lab_ at Carnegie Mellon University; and _David Brin_, author of /_The Transparent Society_/. Some of the other sessions closely related to the Panopticon theme include Terrorizing Privacy? European Developments and Counter Strategies; Intelligent Video Surveillance; Observing Hidden Surveillance Structures; and Art, Surveillance and the Internet. Some of the other important topics include the role of blogging and other nascent communications technology in promoting free speech, explored in the session Unstoppable Speech (or, The Revolution Will Be Podcast); a discussion of Economics of Privacy: Market or Regulation; and The Accountable Internet: Establishing Trust While Preserving Values. In addition to the plenary and breakout sessions, evening "Birds of Feather" cover a wide range of topics. As is traditional at CFP, Tuesday is dedicated to longer sessions. A full-day Workshop on Vanishing Anonymity features over a dozen academic, NGO, and private sector experts discussing authentication techniques, customer, student, traveller and racial profiling, the implications of new technologies such as sousveillance cameras and wearable computing, RFIDs, biometrics, and internet protocols. Tutorials include Biometric Basics, Identity Theft in 2005, International Copyright Law (featuring participants from at least four continents), and _Mike Godwin_'s legendary Constitutional Law in Cyberspace. For those unable to attend in person, most sessions will be blogged, and presentation materials will be available on the web soon after the conference. _______________________________________________ Politech mailing list Archived at http://www.politechbot.com/ Moderated by Declan McCullagh (http://www.mccullagh.org/) ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> ______________________________________________________________ ICBM: 48.07078, 11.61144 http://www.leitl.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE http://moleculardevices.org http://nanomachines.net [demime 1.01d removed an attachment of type application/pgp-signature]

1 0

Re: [tor-talk] Real basic questions for linux
by Maxim Kammerer 06 Jul '18

06 Jul '18

On Tue, Jan 3, 2012 at 20:42, Julian Yon <julian(a)yon.org.uk> wrote: > There's a good reason still to use the Tor Browser: it provides a > "standard" environment which is the same as every* other Tor user's. > Safety in numbers is never truer than with anonymity; compare with the > Black Bloc tactic often used at demonstrations. If everyone looks the > same it's much harder to identify individuals. Tor is an infrastructure with a history of being developed and researched by experts in network security and anonymity. Due to its unique standing in the congregation of similar networks, Tor attracted a fair amount of academic scrutiny, which resulted in many refinements and extensions for resisting various types of attacks, and in documenting its known weaknesses. While I dislike the excessive stiffness of the project (RSA-1024? The 90's called, and they want their b military-grade encryptionb back) and inability to resist the status quo (what again is the reason for not making nodes relay traffic by default? beyond you publishing another conference paper on the oh-so-terrible dangers of that in order to pad your CV, that is), I trust the Tor project to produce something solid and to not grossly overestimate its security and anonymity guarantees. Tor Browser, on he other hand, is just some hack for mangling browser headers. Who develops it? Who scrutinized it? Were it the same people who recommended using the unstable and inadequate Polipo proxy (over-64 MiB files? Nah, never heard of those) instead of well-established Privoxy previously, due to some imaginary perceived limitations of the latter (reading manuals is boring, I guess)? Is there any evidence that Tor Browser prevents fingerprinting which is marginally more sophisticated than looking at some subset of browser headers regardless of their order? Or is the joke that is Panopticlick with its b bits of identifying informationb as state-of-the-art as it gets (mind you, I was able to fool it with Privoxy rules in LibertC), masquerading as TBB, although I know that the specific browser in use can still be fingerprinted differently)? Who cares b let's ship this junk in a bundle, and convince everyone of its utmost necessity. inb4: Yeah, well, that's just, like, your opinion, man. -- Maxim Kammerer LibertC) Linux (discussion / support: http://dee.su/liberte-contribute) _______________________________________________ tor-talk mailing list tor-talk(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk ----- 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

[drone-list] Secrecy News on USAF "incidental" domestic surveillance
by Gregory Foster 06 Jul '18

06 Jul '18

Secrecy News (May 8) - "USAF Drones May Conduct 'Incidental' Domestic Surveillance" by @saftergood <http://twitter.com/saftergood> http://www.fas.org/blog/secrecy/2012/05/usaf_drones.html* * U.S. Air Force policy permits the incidental collection of domestic imagery by unmanned aerial systems (drones), but ordinarily would not allow targeted surveillance of a U.S. person. The Air Force policy was restated in a newly reissued instruction on oversight of Air Force intelligence. "Air Force Unmanned Aircraft System (UAS) operations, exercise and training missions will not conduct nonconsensual surveillance on specifically identified US persons, unless expressly approved by the Secretary of Defense, consistent with US law and regulations," the instruction <http://www.fas.org/irp/doddir/usaf/afi14-104.pdf> stated. On the other hand, "Collected imagery may incidentally include US persons or private property without consent." "Collecting information on specific targets inside the US raises policy and legal concerns that require careful consideration, analysis and coordination with legal counsel. Therefore, Air Force components should use domestic imagery only when there is a justifiable need to do so, and then only IAW [in accordance with] EO 12333, the National Security Act of 1947, as amended, DoD 5240.1-R, and this instruction," it said. Legally valid requirements for domestic imagery, the instruction <http://www.fas.org/irp/doddir/usaf/afi14-104.pdf> said, include surveillance of natural disasters, environmental studies, system testing and training, and also counterintelligence and security-related vulnerability assessments. Air Force units are authorized to acquire domestic commercial imagery for such validated purposes. However, "Air Force intelligence components must not conduct or give the appearance of conducting collection, exploitation or dissemination of commercial imagery or imagery associated products for other than approved mission purposes." See "Oversight of Intelligence Activities," <http://www.fas.org/irp/doddir/usaf/afi14-104.pdf> Air Force Instruction 14-104, April 23, 2012. Another new Air Force Instruction deals with the basic operation of Small Unmanned Aerial Systems in domestic and foreign environments. Among other things, it recommends caution in the use of non-uniformed personnel in conducting drone combat missions. "To ensure the noncombatant status of civilians and contractors is not jeopardized, commanders shall consult with their servicing judge advocate office for guidance before using civilian or contractor personnel in combat operations or other missions involving direct participation in hostilities," the instruction advised. See "Small Unmanned Aircraft Systems Operations," <http://www.fas.org/irp/doddir/usaf/afi11-502v3.pdf> Air Force Instruction 11-502, volume 3, April 26, 2012. In its new mark of the FY2013 defense authorization bill <http://armedservices.house.gov/index.cfm/files/serve?File_id=e7c34102-53e4-…>, the House Armed Services Committee is proposing to provide the Air Force with even more money than it requested for its Predator and Reaper drone programs. See "Congress Funds Killer Drones the Air Force Says It Can't Handle" <http://www.wired.com/dangerroom/2012/05/congress-armed-drones/> by Spencer Ackerman, Wired Danger Room, May 7, 2012. gf -- Gregory Foster || gfoster(a)entersection.org @gregoryfoster<> http://entersection.com/ _______________________________________________ drone-list mailing list drone-list(a)lists.stanford.edu Should you need to change your subscription options, please go to: https://mailman.stanford.edu/mailman/listinfo/drone-list If you would like to receive a daily digest, click "yes" (once you click above) next to "would you like to receive list mail batched in a daily digest?" You will need the user name and password you receive from the list moderator in monthly reminders. Should you need immediate assistance, please contact the list moderator. ----- 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 32
by Patrick R McDonald 06 Jul '18

06 Jul '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 ===================================================== Tahoe-LAFS Weekly News, issue number 32, May 27, 2012 ===================================================== 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`_. If you would like to view the "new and improved" TWN, complete with pictures; please take a `look`_. .. _Tahoe-LAFS: https://tahoe-lafs.org .. _View TWN on the web: https://tahoe-lafs.org/trac/tahoe-lafs/wiki/TahoeLAFSWeeklyNews .. _subscribe to TWN: https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news .. _look: https://tahoe-lafs.org/~marlowe/TWN32.html Announcement and News ===================== TWN Celebrates One Orbit Around the Daystar - ------------------------------------------- Today, we celebrate the one year anniversary of Tahoe-LAFS Weekly News. So many excited things happened in the Tahoe-LAFS universe this past year. We saw the release of Tahoe-LAFS `1.8.3`_, `1.9`_ and `1.9.1`_. There was not `one`_, not `two`_, but `three`_ Tahoe-LAFS Summits. Tahoe-LAFS received a `new server`_. Numerous Tahoe-LAFS grids appeared in `Virginia Tech`_, San Franscisco (`Noisebridge`_) and location unknown (`Cryto Coding Collective`_ and `JonDonym`_). Tahoe-LAFS' influence could be seen in projects like `Nilestore`_, `FreedomBox`_, `Tamias`_ and `Cryptosphere`_. We even saw the founding of a company who donated their work back to Tahoe-LAFS, in `Least Authority Enterprise`_ (LAE) |LAE|. We are really excited in where Tahoe-LAFS is going and that "provider-independent" security is catching on all over. .. _`1.8.3`: http://tahoe-lafs.org/~marlowe/TWN14.html .. _`1.9`: http://tahoe-lafs.org/~marlowe/TWN17.html .. _`1.9.1`: http://tahoe-lafs.org/~marlowe/TWN21.html .. _`one`: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/Summit .. _`two`: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/Summit .. _`three`: https://tahoe-lafs.org/~marlowe/TWN25.html .. _`new server`: http://tahoe-lafs.org/~marlowe/TWN17.html .. _`Virginia Tech`: https://tahoe-lafs.org/~marlowe/TWN18.html .. _`Noisebridge`: http://tahoe-lafs.org/~zooko/TWN13.html .. _`Cryto Coding Collective`: https://tahoe-lafs.org/~marlowe/TWN30.html .. _`JonDonym`: http://tahoe-lafs.org/~marlowe/TWN16.html .. _`Nilestore`: http://tahoe-lafs.org/~zooko/TWN11.html .. _`FreedomBox`: http://tahoe-lafs.org/~marlowe/TWN17.html .. _`Tamias`: http://tahoe-lafs.org/~marlowe/TWN20.html .. _`Cryptosphere`: https://tahoe-lafs.org/~marlowe/TWN24.html .. _`Least Authority Enterprise`: http://tahoe-lafs.org/~marlowe/TWN15.html Thoughts from the Scribe - ------------------------ When Zooko |zooko| suggested I write a weekly Tahoe-LAFS newsletter a year ago, I was a little unsure. I was not sure what I would write about or if I would be able to provide stories which would capture the attention of the incredible community surrounding Tahoe-LAFS. I must say now that I am ever so grateful for this opportunity. I can't express my thanks enough, but I will do my very best to below. First, I would like to thank the readers. If it wasn't for you, this newsletter, wouldn't exist. Your exceptional feedback (see below) makes writing TWN a sheer joy. I look forward to doing this every week and that is in large part due to you. I would like to thank the development and support team of Tahoe-LAFS. Thank you for the gift of Tahoe-LAFS. I hope I help more people realize what a special thing we have here. In particular, I would like to thank Zooko, Brian |brian| and David-Sarah |davidsarah|. Your brilliant discussions on the mailing list and IRC stretched the limits of my brain, forcing me to look up numerous things. Thank you so much for expanding my knowledge. Thank you to Peter |peter|. Your interview helped convince me that I didn't need to be a developer to contribute to an OSS project in a meaningful way. That interview did more to encourage me to continue than you will ever know. Thanks to Kevan |kevan| for being my first interview. Thanks to Marcus |marcusw| for forwarding me all the tab completion fails :). Lastly, thanks to the many whom, I didn't get to mention. You have made me a better person and not just technically. Thank you from the bottom of my heart. Thank You to Atlas Networks - --------------------------- We would like to say thank you to `Atlas Networks`_ |AtlasNetworks| for their continued support and generous donation of four servers. As noted in `TWN #14`_, "In addition to the generosity of their hardware donation, Atlas Networks provide the Tahoe-LAFS project with remote consoles and technical support, including complete OS reinstalls." As a way of showing my appreciation, I will be moving my last VPS over to Atlas Networks. Thank you for your support. .. _Atlas Networks: http://atlasnetworks.us .. |AtlasNetworks| image:: AtlasNetworks.png :height: 35 :alt: Atlas Networks :target: http://atlasnetworks.us .. _`TWN #14`: https://tahoe-lafs.org/~marlowe/TWN14.html Redundant Array of Independent Clouds Makes a Big Splash - -------------------------------------------------------- The `article on RAIC`_ in last week's TWN made a tremendous splash. Numerous tweets regarding it appeared on Twitter. The following, "Redundant Array of Independent Clouds -- Dropbox, Googledrive, memopal, ... http://j.mp/MviO55" [`0`_] was retweeted 22 times and favorited by 41 users. Numerous other news channels picked it up and ran with the story. TWN experienced a large increase in the number of subscribers this past week. My feelings tell me it was largely a result of this story. So congratulations to Deigo "sickness" Righi |sickness|, your idea resonates with a lot of people. .. _`article on RAIC`: https://tahoe-lafs.org/~marlowe/TWN31.rst .. _`0`: https://twitter.com/newsycombinator/status/203984643253477376 Free/Open Source Project of the Week - ------------------------------------ One of the `first FOSS projects`_ we wrote about was `git-annex`. Back then, Tahoe-LAFS was made a `backend`_ to git-annex. git-annex is a tool that uses all of git's machinery for identifying and tracking files, but stores the actual complete contents of the files in a separate location instead of in the git repo itself.Now the developer, Joey Hess, is in the middle of a very ($9,842 pledged) successful `Kickstarter campaign`_. Congratulations Joey on achieving your funding and we look for to the new features which result. .. _`first FOSS projects`: https://tahoe-lafs.org/~marlowe/TWN1.html .. _`git-annex`: http://git-annex.branchable.com/ .. _`backend`: http://git-annex.branchable.com/special_remotes/ .. _`Kickstarter campaign`: http://www.kickstarter.com/projects/joeyh/git-annex-assistant-like-dropbox-… Glowing Quotes ============== Two glowing quotes this week. The first comes from a user, Saint Germain, in `response to answers to their question`_ "Wow, you guys don't do things by half... I was not expecting such a detailed answer ! After 12 years on linux, it never ceases to amaze me how open and friendly the open source community is." This last set is regarding the TWN. I would like to personally thank, j_s and Zooko for such glowing personal reviews. "whoever put together this newsletter is clearly doing a great job for that community" [`1`_] "Amen!! Patrick "marlowe" McDonald has really given us a gift by publishing the Tahoe-LAFS Weekly News every week. We're coming up on the Tahoe-LAFS Weekly News one-year anniversary next week. b:" [`2`_] .. _`response to answers to their question`: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007368.html .. _`1`: https://news.ycombinator.com/item?id=3997429 .. _`2`: https://news.ycombinator.com/item?id=3997548 Tahoe-LAFS on Twitter ===================== @SGgrc have you ever looked at Tahoe-LAFS (distributed encrypted filessytem) http://bit.ly/K26V47 [`3`_] This is awesome - a redundant, distributed file system: tahoe-lafs http://buff.ly/L7NtQM [`4`_] Here's the entry in Duplicati's blog where they announce the addition of Tahoe-LAFS backend: http://identi.ca/url/69931029 [`5`_] .. _`3`: https://twitter.com/tvgtvg/status/204143972778639360 .. _`4`: https://twitter.com/ddrager/status/204195040120143872 .. _`5`: https://twitter.com/zooko/status/205002859576705024 - From the tahoe-dev Mailing List =============================== Potential use of personal backup - -------------------------------- As mentioned above, a new user, Saint Germain was unsure of Tahoe-LAFS' ability to be used for `personal backups`_. Guido Witmond included some of the reasons to use Tahoe-LAFS for personal backup: * it's easy to setup, although not yet "Parent-proof"; * it works out-of-the-box on many platforms; * it is encrypted by default; * only you have the key, so no one else can read your data, unlike the other cloud providers; * that it shows the 'health' of your data; and allows to repair it. [`6`_] Zooko provided one of the better `descriptions of Tahoe-LAFS`_, I have experienced the privileges to read. I may have to steal it and place it in the introductory documentation. On a side note, Saint Germain is writing an article on new backup software for the French site, linuxfr.org and may add Tahoe-LAFS to the article. Regardless of whether the article includes Tahoe-LAFS, we would love to see it. .. _`personal backups`: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007349.html .. _`6`: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007350.html .. _`descriptions of Tahoe-LAFS`: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007365.html Patches Needing Review of the Week ================================== There is one (1) ticket still needing review for 1.9.2: * `#1115`_: add servers-of-happiness to reports (post-repair says 10 hosts have good shares but there only 4 hosts) There are five (5) ticket still needing review for 1.10.0: * `#937`_: 'tahoe run' doesn't work for an introducer node * `#1539`_: stop putting pkg_resources.require() into .tac files * `#1159`_: stop using .tac files: make it possible to change appname, Python package-directory name, perhaps other names * `#1693`_: flogtool doesn't get automatically provided * `#1240`_: add functional test of ResponseCache in favour of MDMFSlotReadProxy's cache There are three (3) tickets still needing review of 1.11.0: * `#1265`_: New Visualizer is insufficiently labelled/documented (plus layout problem) * `#1382`_: immutable peer selection refactoring and enhancements * `#1569`_: rerecord and review pluggable backends for landing on trunk .. _`#1115`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1115 .. _`#937`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/937 .. _`#1539`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1539 .. _`#1159`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1159 .. _`#1693`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1693 .. _`#1240`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1240 .. _`#1265`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1265 .. _`#1382`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1382 .. _`#1569`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1569 - ---- *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* |marlowe| *, 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:: zooko.png :height: 35 :alt: zooko :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |peter| image:: psecor.jpg :height: 35 :alt: peter :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |marlowe| image:: marlowe-x75-bw.jpg :height: 35 :alt: marlowe :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |davidsarah| image:: davidsarah_bw.png :height: 35 :alt: davidsarah :target: http://tahoe-lafs.org/trac/tahoe-lafs/wikiAboutUs .. |brian| image:: warner.png :height: 35 :alt: brian :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |marcusw| image:: marcus.png :height: 35 :alt: marcusw .. |sickness| image:: sickness.jpg :height: 35 :alt: sickness .. |kevan| image:: kevan.png :height: 35 :alt: kevan .. |LAE| image:: LAE.png :height: 35 :alt: Least Authority Enterprises :target: http://leastauthority.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPw4KSAAoJEAT4nRyi0elySjIQAIcO9HPlFHdzWEKe3kAuN4ge npM99S86Iu5MiUVtc3+xA2dNEP++egISngHuiZrNYoomQbeMec3aX5VjWHr8fple wl6mhH1EJiEpBE54g6G7BlCDMrhVs53tpN0cShw7kTEtSwyjhuMtklbJaDyuxgRY V8cvarGe6l0RZf7+YWiTwl7CLVCWNXciKFMxBGCaem1iOx29TSIEMXW1Y7sVbLl7 xrK+mPdUcGM7YhLRfvnRPq8kgRBnZ9c1+Ovycp+X8/6Lvj3mu5aRndsSZDU6+tZa SdRmgIPHSNV/Cox5D1YdqSXmv+eJg+2qfH6ZPsD16QpoYoNAcBnlLaoaOn4N39Nh Yg4JASDtpLnVxJOVeSu7ROtRIJBB8ZK0E/Xfgt4C4JFR3oKVPAsqAuWhhL1qjXt8 VXf9MSu23u2AJ13CdjTw666NRRoTzf3DYodoXOJ1TWKy0QaC0gvR7z2xKxPzegAK TrvW6ksceloEOQNBRxEnRzzEqxo79GRAGywWPeR8dJq67PRo4w47nZfz/z1im12R a/T5/u24fMC8yGKbpN6QXpp7QUmJcKM+6fBYbk34pYp7eUpTmlmByogR02THt59y OAMXZlA3DRNn9HIgekcz92Bx3USNpZ2uN3yifRON48vJMR9P9nqy7awWckl1XZMw 3y7qV3YYNiP8C3fLhbl0 =WKuv -----END PGP SIGNATURE----- _______________________________________________ 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

Re: [tahoe-dev] tahoe-lafs 1.9.1 shipped in the next Debian stable
by Zooko Wilcox-O'Hearn 06 Jul '18

06 Jul '18

Dear Bertagaz: We're almost ready to release Tahoe-LAFS v1.9.2, and I wonder if it is okay to take a couple more days for extra testing or if we should hurry and finalize it so you can package it for Debian? We've fixed all but one of the issues that we intended to fix. You can see the issue tickets here: https://tahoe-lafs.org/trac/tahoe-lafs/milestone/1.9.2 The one serious issue that isn't fixed yet is https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1670# KeyError in mutable retrieve We know of a bug in the code (dict instead of tuple being returned from get_verinfo() of MDMFs), but we're not sure if that bug is causing that failure. There is no unit test currently demonstrating that failure. We prefer not to fix bugs when we don't have a unit test that goes from red to green by that fix, so if it won't make us miss the Debian deadline, I'd like to take a couple more days to figure out how to write a unit test of #1670. Then we'll find out if the dict-instead-of-tuple bug is causing #1670 or not. Also I'm doing an experiment of converting all of the existing unit tests from using SDMFs to using MDMFs as a way to find any bugs in MDMFs. So far I haven't found any more bugs in MDMFs that way. (Because there were already quite a few tests of MDMFs.) Also, it would be great to have some actual users try out 1.9.2 before we finalize it. Users! You can do this right now if you're willing to use darcs to fetch the source. This is actually painless -- you just acquire darcs (http://wiki.darcs.net/Binaries) and then you run darcs get --lazy https://tahoe-lafs.org/source/tahoe-lafs/1.9.2 Then you never have to touch darcs again. That command takes about 60 seconds to run. Oh, but it might fail if the darcs binary you got is incapable of handling HTTPS. In that case, you give up and complain to us and we'll post some tar.gz files for you to try out... Regards, Zooko _______________________________________________ tahoe-dev mailing list tahoe-dev(a)tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev ----- 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

Dealing with the Washington media -- survivors speak out
by Declan McCullagh 06 Jul '18

06 Jul '18

[I first moved to Washington in 1991, and I've been living here off and on ever since. (Yes, this is sad.) Here's one view of what it's like to deal with the Washington media, with perspectives from those who have had run-ins with us before. It's from a very nice "Survivor's Guide for Presidential Nominees" just out from the Brookings Institution. --Declan] http://www.appointee.brookings.org/sg/c6.htm A Survivor's Guide for Presidential Nominees Dealing with the Media "The first rule of survival in Washington is never do or say anything that you dont want to read about on the front page of The Washington Post." If youve always hankered for closer attention from the news media, youve come to the right town. Washington is crawling with reporters nearly 5,000 are accredited by the House and Senate press and broadcast galleries and hardly a nook or cranny of the government goes unexplored by some branch of the media, from the national newspapers and networks to pricey newsletters and trade publications that are the bibles of their industries. Washington is a fish bowl, and if you want to make a name for yourself, this is the place to do it. But it may not be quite the name you had in mind. The Washington media are known more for the reputations they tear down than the ones they build up. Many prospective nominees have dealt with reporters before in state houses, the business world, the military or on Capitol Hill itself, where legions of assistants make a living trying to figure out how to get or keep their bosses in the spotlight. But now youre in a different situation. Be forewarned: No matter how much or how little you dealt with the media before coming to Washington, its usually a surprise when you stand in the batters box here for the first time to discover how fast they throw and how much those sliders break. For that reason, keep in mind three basic pieces of advice. First, be very careful what you say to reporters while yours is just one of several names the White House is considering. Second, dont say anything at all to the press, on the record or off, while the Senate is considering your nomination. And third, never lie to the media it will come back to haunt you. In this chapter, well look at the role that journalists play in the nations capital and its political process. Then well get practical advice from those who have gone through the nomination and confirmation process, as well as from those in the media who have watched and covered hundreds of important nominations. The Capital of the News World The capital of the country is also the capital of the news world. New York can still lay claim to being the headquarters of the three original television networks, two news magazines, the major news service and two of the nations finest newspapers (The New York Times and The Wall Street Journal), but the news organizations Washington bureaus are the crown jewels of their news operations. Two nationally recognized papers, The Washington Post and USA Today, are produced inside the Beltway. CNNs home may be in Atlanta, but much of its hard news originates from its bureau next to Washingtons Union Station. National Public Radio has its studios and nerve center here, and the Public Broadcasting System is across the river in Alexandria, Va. Reporters who ply their craft in Washington may be no more talented than their colleagues in state capitals and other major cities, but they have a singular advantage: More news happens here than in any other single city on the planet and the local scribes get to cover it. They get to see the world with the president from Air Force One and trudge through the snows of New Hampshire with the candidates. When they hold a banquet to salute (or laugh at) themselves, the guest of honor is not the mayor or the governor, but the president of the United States. Love them or loathe them, they are the publics eyes and ears. Your deeds and reputation in office will pass through the medias filters before they become known to the public at large. As frustrating as the media can be, Washington insiders keep close tabs on the news. Many officials read several major newspapers religiously, making sure to check the Federal Page in The Washington Post and the Inside the Beltway column in The Washington Times, among other regular features. If you want to prepare for a rigorous questioning, watch journalists pepper a White House official on one of the weekend talk shows. The latest scandals In recent years, the line between the tabloids and the mainstream press has blurred as news organizations rush to mine the latest political sex scandals, from John F. Kennedys Hollywood conquests to Gary Harts escapades on a yacht to Bill Clintons trysts with an eager intern. What once was fodder only for the Drudge Report is front-page news in the broadsheets especially since Matt Drudges most sensational morsels proved largely on target. The airwaves and Internet are saturated with news, but readership and viewership are flagging. Reporters can live without respect they almost relish being regarded as a royal pain but losing credibility and audience pains them deeply. Reporters take themselves seriously too seriously for some of their subjects taste. The quicker a newspaper or news broadcast is to expose a public servants failings and foibles, the thinner its own hide. Newspapers have gotten better in recent years about publishing corrections, but they are still quicker to confess error about dates or the spelling of names or identities in a picture than to own up to getting the whole thing wrong or lopsided. Reporters and editors also pride themselves on breaking news, even if their scoop remains exclusive only for hours or even minutes. A newspaper may devote 10 inches of space to an appointment if it is given the details exclusively, or pries them loose, one day in advance. Announce the appointment at the same time for all the media to see, and it may not rate so much as a paragraph. Many public officials today would subscribe to the sentiments that a character in a Tom Stoppard play expressed: "Im with you on the free press. Its the newspapers I cant stand." Reporters respond with their highest authority on these matters: Thomas Jefferson. The author of the Declaration of Independence observed in a 1787 letter: The basis of our government being the opinion of the people, the very first object should be to keep that right; and were it left to me to decide whether we should have a government without newspapers, or newspapers without a government, I should not hesitate a moment to prefer the latter. But I should mean that every man should receive those papers and be capable of reading them. The papers of Jeffersons day boiled with shamelessly partisan rhetoric, barb and propaganda and were hardly deserving "of such high praise as agencies of public enlightenment," as Jefferson biographer Dumas Malone put it. But Jeffersons point stands: The press has an important role to play in a democracy. And when news erupts, those obstreperous reporters camped outside your office and sometimes on your lawn wont let you forget it. Although the press plays a critical role in our democracy, even some reporters admit misgivings about their techniques. Janet Malcolm, the author and contributor to The New Yorker, offered this ominous warning to the unwary in her 1990 book, The Journalist and the Murderer: "Every journalist who is not too stupid or full of himself to notice what is going on knows that what he does is morally indefensible. He is a kind of confidence man, preying on peoples vanity, ignorance or loneliness, gaining their trust and betraying them without remorse." That may be a gross exaggeration, but it has a kernel of truth. Journalists do want to gain your confidence and its not because they want to be your friends. "Reporters are professionals whose loyalty is to their media outlets or their profession, not to you," says Wayne Pines, former spokesman for the Food and Drug Administration and now a public relations counselor with APCO Associates. "Knowing them personally means you may get the benefit of the doubt in a difficult situation, and you may also get to go on background and influence a story anonymously but only after you have established a trusting relationship. In Washington, never lie to the media, dont mislead them, dont get angry with them and dont underestimate their influence. They will influence what most of the world, including your own employees, think of you." Get it first and right From the journalists perspective, there is one cardinal rule: Get it first, but first get it right. Early in the Clinton administration, Tim Russert of NBCs "Meet the Press" jumped on the air in advance of a presidential news conference to announce the name of the presidents new puppy. Unfortunately, his sources had led him astray and he got it wrong. Why risk being wrong on the name of a dog, much less the name of a nominee? Journalists generally wont take that risk unless they are certain of the story. They always want to show up the competition. Keep in mind that, even if the new administration is trying to keep the names of potential nominees under wraps, reporters by nature are extremely competitive and very clever. When Thurgood Marshall retired from the Supreme Court, reporters quickly found out who was on George Bushs short list. The White House managed to spirit Clarence Thomas up to Walkers Point, the presidents summer compound in Kennebunkport, Maine, for the July 1, 1991, announcement without anyones spotting the future justice or breaking the news of his selection. But Associated Press reporter Rita Beamish found out ahead of time who it wasnt. She called the other candidates at home where they were sitting by the phone awaiting a call from the White House and correctly deduced that "those who were still home with no flight plans were not the chosen ones." Barbara Bush, in her memoir, tipped her hat to Beamish for this "great ingenuity." Reporters have a knack for unearthing conflict, even within organizations that are paragons of harmony. The many things on which you and a Cabinet secretary or the president see eye-to-eye may be of little or no interest, but where you disagree is news. Reporters will mine the new administration for evidence of disputes between a president and the Cabinet, between the Cabinet and the Office of Management and Budget and, naturally, between the administration and Congress. Sources in Congress generally the most accessible and open-mouthed branch of the government often are eager to help reporters root around. Interest groups with ties deep into the bureaucracy will throw logs onto the fire as well. Puncturing a new enterprise When reporters are covering a new enterprise, including the start of an administration, they are like small children playing with balloons at a birthday party. Its great fun to fill them up with air, but even greater fun to puncture them. If you are new to Washington and public life, expect such treatment. Reporters will write introductory accounts that extol your talents and recite your exploits in ways so flattering that no one save your mother could possibly believe them. And later, if something goes wrong on your watch, you quickly may find yourself the almost unrecognizable villain of a piece written by the same hand that produced your hagiography. Lani Guinier, President Clintons unsuccessful nominee for civil rights enforcer in 1993, lamented afterward to National Public Radio, "Even my own mother couldnt recognize me in the press coverage that I received." The media are avid for news. Whether by friendly takeover (as when George Bush succeeded Ronald Reagan in 1989) or a hostile one (as when Bill Clinton ousted Bush in 1993), a change of administrations affords an ample supply of headlines for news-hungry reporters and editors. Newspapers will run stories by the score on who will get what post, devoting yards of space to programs and positions that wont rate a mention in the years that follow. The political masterminds of the victorious campaign, flush with success, will keep the press corps spinning with announcements and trial balloons, even as the new presidents team works frantically behind closed doors to get at least some of its act together by noon on Jan. 20. They will trade in names perhaps your name among them because journalists are hungry for scoops, and these are "secrets" that cost little to give away. Sometimes that is all you will actually get: your name mentioned on the insiders short list, a consolation prize if you are denied the actual nomination. The erstwhile campaigners may also run your name up the pole to see who salutes or shoots. Unless an administration comes in on the run as Ronald Reagan and his team did in 1981 the press soon will turn its attention to the disarray and vacancies throughout the government, as was conspicuously the case in 1993 for Bill Clinton and the gang from the war room in Little Rock. As political scientist James Pfiffner of George Mason University recounted in a 1996 update to his book, The Strategic Presidency, it took Clinton 8.5 months on average to get his executive branch appointees confirmed after the inauguration. That was six months longer than Kennedy, and probably "the slowest in history," Pfiffner found. It was easy pickings for a press corps always eager to unearth early signs of confusion. When in Doubt, Dont Talk You wont be surprised to hear that savvy confirmation hands such as lobbyist and former Nixon White House official Tom Korologos, former presidential appointees and those who work on Capitol Hill all agree: be very circumspect in talking with reporters before your nomination and even more so before your confirmation. But it might surprise you to hear prominent reporters echo the same advice. Broadcast journalist Brit Hume, who has watched administrations come and go for three decades, minces no words: "If they havent been named, and they havent been picked, and they havent been talked to, they really have no reason to talk to the press. When in doubt, dont talk to the press." Still, "you want to be pleasant to reporters, polite to them," says Hume, managing editor and chief Washington correspondent for Fox News and a former ABC White House correspondent. He adds: Treat them as if you know theyve got a job to do, that you understand and you sympathize, and if you cant comment, just say, "Look, I know youve got work to do, and Im sorry. I cant comment about this stuff at this time. I apologize. I just cant." And then dont. The right to remain silent Freedom of the press is a cherished right under the First Amendment. While there is no concomitant freedom from the press in the Constitution, you do have a right to remain silent or, better yet, to refrain politely from answering reporters questions. But many people fail to exercise that right. They often let their egos override their common sense. It is, as Samuel Johnson said of second marriages, the triumph of hope over experience. People beguile themselves into believing that for once a news report is going to spotlight their innocence, brilliance or cleverness instead of reminding us how adroit a questioner the reporter is. Dont make the mistake of thinking that you can enhance your chances of being appointed by talking openly and frankly with the press. As Hume observes, "the chances of your saying just the right thing and having it come out sounding just the right way are sufficiently remote that its not worth risking." Another White House press corps veteran, Gene Gibbons, says, "My two rules of life for people who find themselves in the media spotlight are: never lie, and dont be afraid to tell the media to take a hike." Gibbons, former White House correspondent for Reuters and now the managing editor of Stateline.org, the Web site for state house reporters, says, "The first rule of survival in Washington is never do or say anything that you dont want to read about on the front page of The Washington Post." He believes that a candidate who has been asked by the White House not to discuss an overture has only two choices in handling questions from the media: "Either say no comment or screen your calls." Diana Huffman, who observed the nominations process from the very different perspectives of managing editor of the National Journal and staff director of the Senate Judiciary Committee, says, "Youre ahead in the game if the first publicity comes when the White House actually announces its intention to nominate you." Others agree. Pines, the former Food and Drug Administration spokesman who specializes in crisis communication, says, "The only people who speak with the media in advance of being nominated are those who feel their nominations are on the ropes and they have nothing to lose, or who are not going to take the job and want the visibility that goes with having been considered. If I asked someone I was considering for a job not to speak with the media, and he or she did, I would cross that person off my list." Cheryl Arvidson, a longtime Washington political reporter, counsels, "It is extremely important for a potential nominee not to play favorites and not to engage in cat-and-mouse with reporters." If a reporter asks to talk with you off the record or on background, "caution should be the watchword," says Arvidson, now senior writer for the Freedom Forum, the free press and free speech foundation that operates the Newseum in Arlington, Va. If a reporter calls looking for background information, it may be possible for the prospect (or a surrogate) to point out things in the public record, but usually that isnt necessary, Arvidson says. "The good reporters will find those things on their own, and they will also find people who know the would-be nominee." The LBJ rule Stephen Potts, the director of the U.S. Office of Government Ethics in the Bush and Clinton administrations, subscribes to the view that prospective nominees those not yet officially announced by the White House should talk to few people outside a tight circle of family and colleagues about an impending and still uncertain career switch. "In the Lyndon Johnson years, LBJ had a general rule that if it leaked to the press that you were going to be nominated by him, you therefore were not going to be nominated," he says. "It was that straightforward. So people in those years had a very powerful incentive to keep their mouths shut." That may sound imperious, but if the White House cant trust someone to keep a confidence before taking the job, how can it expect that person to be a team player once confirmed? The rules may not be so ironclad anymore. But presidential transitions inspire a lot of self-promotion, and much of that backfires. The hordes of reporters camped out in Little Rock with President-elect Clinton and his team during the 1992 transition were hungry for word of who was in the running for Cabinet posts. But they guffawed when one Democratic lawmaker and his staff let it be known that he was a candidate for everything from secretary of Defense to CIA director. "It didnt take reporters long to get Clinton insiders laughing about his audacity over drinks in various Little Rock watering spots," a scribe recalls. "And before he knew it, the congressman was a laughing stock." The congressman never got any of the jobs that he and his press agents talked about. Telling the Truth Agreement is universal on another rule of behavior for dealing with reporters: never lie. "Dont ever be in a situation of denying it if you actually know anything. You cant compromise your own integrity," says a Bush administration official, who adds with a laugh, "Of course, its possible that the press has heard about it before you have." Donald C. Alexander recalled that when word leaked out of the Nixon White House about his appointment as IRS commissioner, he followed the advice of George P. Shultz, then secretary of the Treasury, and "did the neither confirm nor deny bit." Alexander added: "George told me, You dont want to lose your credibility even before you get here wait to lose it when you get here." Alexander helped insulate the IRS from Nixon White House excesses during the aftermath of Watergate. He twice had to testify before grand juries, but the ordeal he remembered most is going before congressional oversight committees, where Democrats gave him a tough going-over: You could always tell if the hearing was going to be a total disaster if there were four or more stand-up cameras in the room. That meant the committee had told the press they were really going to go for the jugular. If there were no cameras, the press didnt care for the hearing, and that meant the hearing was likely to be constructiveYou could just tell as you were walking down the halls in Rayburn [House Office Building]. If the light coming out of the hearing room was very bright, it was "Oh, God, here we go again!" * When in doubt, dont talk with reporters. It could cost you an administration post. Regardless of the situation, youre under no obligation to answer reporters questions. * When you do talk with reporters, dont lie or mislead them. * Dont expect them to report everything you say. Print and broadcast reporters alike will cull what they consider your most interesting or salient comments. * Dont be rude or peremptory. Reporters have an important job to do. * Stay abreast of the news. ### ----- End forwarded message -----

1 0

[Politech] Computers Freedom and Privacy conference in Seattle from Apr 12-15 [priv]
by Declan McCullagh 06 Jul '18

06 Jul '18

[Any Politechnicals going? I'm teaching a graduate public policy course this semester -- the last class meets on April 16, so I'm not sure if I'm going to be able to make it to Seattle. It would have to be a quick trip, at least for me. --Declan] -------- Original Message -------- Subject: CFP - post to politech list? Date: Wed, 16 Mar 2005 14:09:40 -0800 From: Deborah Pierce <dsp(a)privacyactivism.org> To: declan(a)well.com Hi Declan, Would you post this to your list. I'd like to remind everyone to book early for the conference while we still have the good rates and discounts! I've also highlighted a few of the panels that will take place at this year's conference. Thanks, Deborah Pierce PrivacyActivism Chair, CFP2005 A _detailed program_ for the 15th annual ACM Conference on Computers, Freedom, and Privacy is available on the _CFP2005 website_. CFP2005 will be held at the Westin Hotel in Seattle, WA, April 12-15, 2005. Discounted registration, and special conference rates at the Seattle Westin remain available through March 21, register before that date in order to get the advance discounts. This year's theme is _Panopticon_: Over time, and particularly recently, surveillance of ordinary citizens has increased to dramatic levels. Not only are governments watching more aspects of their citizens' lives, but those in the private sector are increasing surveillance of people as well. Often lost in the race to "increase intelligence" are discussions about different approaches to address problems like the threat of terrorism that are equally or more effective, but do not involve extensive and constant surveillance. The opening plenary debate focuses on "Sousveillance in the Panopticon?. Panel members include _Dr. Steve Mann_, Director of the eyeTap Personal Imaging Lab at the University of Toronto, known for his work in wearable cameras and computing; _Dr. Latanya Sweeney_, Director of the _Data Privacy Lab_ at Carnegie Mellon University; and _David Brin_, author of /_The Transparent Society_/. Some of the other sessions closely related to the Panopticon theme include Terrorizing Privacy? European Developments and Counter Strategies; Intelligent Video Surveillance; Observing Hidden Surveillance Structures; and Art, Surveillance and the Internet. Some of the other important topics include the role of blogging and other nascent communications technology in promoting free speech, explored in the session Unstoppable Speech (or, The Revolution Will Be Podcast); a discussion of Economics of Privacy: Market or Regulation; and The Accountable Internet: Establishing Trust While Preserving Values. In addition to the plenary and breakout sessions, evening "Birds of Feather" cover a wide range of topics. As is traditional at CFP, Tuesday is dedicated to longer sessions. A full-day Workshop on Vanishing Anonymity features over a dozen academic, NGO, and private sector experts discussing authentication techniques, customer, student, traveller and racial profiling, the implications of new technologies such as sousveillance cameras and wearable computing, RFIDs, biometrics, and internet protocols. Tutorials include Biometric Basics, Identity Theft in 2005, International Copyright Law (featuring participants from at least four continents), and _Mike Godwin_'s legendary Constitutional Law in Cyberspace. For those unable to attend in person, most sessions will be blogged, and presentation materials will be available on the web soon after the conference. _______________________________________________ Politech mailing list Archived at http://www.politechbot.com/ Moderated by Declan McCullagh (http://www.mccullagh.org/) ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> ______________________________________________________________ ICBM: 48.07078, 11.61144 http://www.leitl.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE http://moleculardevices.org http://nanomachines.net [demime 1.01d removed an attachment of type application/pgp-signature]

1 0

Re: [tor-talk] Real basic questions for linux
by Maxim Kammerer 06 Jul '18

06 Jul '18

On Tue, Jan 3, 2012 at 20:42, Julian Yon <julian(a)yon.org.uk> wrote: > There's a good reason still to use the Tor Browser: it provides a > "standard" environment which is the same as every* other Tor user's. > Safety in numbers is never truer than with anonymity; compare with the > Black Bloc tactic often used at demonstrations. If everyone looks the > same it's much harder to identify individuals. Tor is an infrastructure with a history of being developed and researched by experts in network security and anonymity. Due to its unique standing in the congregation of similar networks, Tor attracted a fair amount of academic scrutiny, which resulted in many refinements and extensions for resisting various types of attacks, and in documenting its known weaknesses. While I dislike the excessive stiffness of the project (RSA-1024? The 90's called, and they want their b military-grade encryptionb back) and inability to resist the status quo (what again is the reason for not making nodes relay traffic by default? beyond you publishing another conference paper on the oh-so-terrible dangers of that in order to pad your CV, that is), I trust the Tor project to produce something solid and to not grossly overestimate its security and anonymity guarantees. Tor Browser, on he other hand, is just some hack for mangling browser headers. Who develops it? Who scrutinized it? Were it the same people who recommended using the unstable and inadequate Polipo proxy (over-64 MiB files? Nah, never heard of those) instead of well-established Privoxy previously, due to some imaginary perceived limitations of the latter (reading manuals is boring, I guess)? Is there any evidence that Tor Browser prevents fingerprinting which is marginally more sophisticated than looking at some subset of browser headers regardless of their order? Or is the joke that is Panopticlick with its b bits of identifying informationb as state-of-the-art as it gets (mind you, I was able to fool it with Privoxy rules in LibertC), masquerading as TBB, although I know that the specific browser in use can still be fingerprinted differently)? Who cares b let's ship this junk in a bundle, and convince everyone of its utmost necessity. inb4: Yeah, well, that's just, like, your opinion, man. -- Maxim Kammerer LibertC) Linux (discussion / support: http://dee.su/liberte-contribute) _______________________________________________ tor-talk mailing list tor-talk(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk ----- 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

[drone-list] Secrecy News on USAF "incidental" domestic surveillance
by Gregory Foster 06 Jul '18

06 Jul '18

Secrecy News (May 8) - "USAF Drones May Conduct 'Incidental' Domestic Surveillance" by @saftergood <http://twitter.com/saftergood> http://www.fas.org/blog/secrecy/2012/05/usaf_drones.html* * U.S. Air Force policy permits the incidental collection of domestic imagery by unmanned aerial systems (drones), but ordinarily would not allow targeted surveillance of a U.S. person. The Air Force policy was restated in a newly reissued instruction on oversight of Air Force intelligence. "Air Force Unmanned Aircraft System (UAS) operations, exercise and training missions will not conduct nonconsensual surveillance on specifically identified US persons, unless expressly approved by the Secretary of Defense, consistent with US law and regulations," the instruction <http://www.fas.org/irp/doddir/usaf/afi14-104.pdf> stated. On the other hand, "Collected imagery may incidentally include US persons or private property without consent." "Collecting information on specific targets inside the US raises policy and legal concerns that require careful consideration, analysis and coordination with legal counsel. Therefore, Air Force components should use domestic imagery only when there is a justifiable need to do so, and then only IAW [in accordance with] EO 12333, the National Security Act of 1947, as amended, DoD 5240.1-R, and this instruction," it said. Legally valid requirements for domestic imagery, the instruction <http://www.fas.org/irp/doddir/usaf/afi14-104.pdf> said, include surveillance of natural disasters, environmental studies, system testing and training, and also counterintelligence and security-related vulnerability assessments. Air Force units are authorized to acquire domestic commercial imagery for such validated purposes. However, "Air Force intelligence components must not conduct or give the appearance of conducting collection, exploitation or dissemination of commercial imagery or imagery associated products for other than approved mission purposes." See "Oversight of Intelligence Activities," <http://www.fas.org/irp/doddir/usaf/afi14-104.pdf> Air Force Instruction 14-104, April 23, 2012. Another new Air Force Instruction deals with the basic operation of Small Unmanned Aerial Systems in domestic and foreign environments. Among other things, it recommends caution in the use of non-uniformed personnel in conducting drone combat missions. "To ensure the noncombatant status of civilians and contractors is not jeopardized, commanders shall consult with their servicing judge advocate office for guidance before using civilian or contractor personnel in combat operations or other missions involving direct participation in hostilities," the instruction advised. See "Small Unmanned Aircraft Systems Operations," <http://www.fas.org/irp/doddir/usaf/afi11-502v3.pdf> Air Force Instruction 11-502, volume 3, April 26, 2012. In its new mark of the FY2013 defense authorization bill <http://armedservices.house.gov/index.cfm/files/serve?File_id=e7c34102-53e4-…>, the House Armed Services Committee is proposing to provide the Air Force with even more money than it requested for its Predator and Reaper drone programs. See "Congress Funds Killer Drones the Air Force Says It Can't Handle" <http://www.wired.com/dangerroom/2012/05/congress-armed-drones/> by Spencer Ackerman, Wired Danger Room, May 7, 2012. gf -- Gregory Foster || gfoster(a)entersection.org @gregoryfoster<> http://entersection.com/ _______________________________________________ drone-list mailing list drone-list(a)lists.stanford.edu Should you need to change your subscription options, please go to: https://mailman.stanford.edu/mailman/listinfo/drone-list If you would like to receive a daily digest, click "yes" (once you click above) next to "would you like to receive list mail batched in a daily digest?" You will need the user name and password you receive from the list moderator in monthly reminders. Should you need immediate assistance, please contact the list moderator. ----- 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 32
by Patrick R McDonald 06 Jul '18

06 Jul '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 ===================================================== Tahoe-LAFS Weekly News, issue number 32, May 27, 2012 ===================================================== 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`_. If you would like to view the "new and improved" TWN, complete with pictures; please take a `look`_. .. _Tahoe-LAFS: https://tahoe-lafs.org .. _View TWN on the web: https://tahoe-lafs.org/trac/tahoe-lafs/wiki/TahoeLAFSWeeklyNews .. _subscribe to TWN: https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news .. _look: https://tahoe-lafs.org/~marlowe/TWN32.html Announcement and News ===================== TWN Celebrates One Orbit Around the Daystar - ------------------------------------------- Today, we celebrate the one year anniversary of Tahoe-LAFS Weekly News. So many excited things happened in the Tahoe-LAFS universe this past year. We saw the release of Tahoe-LAFS `1.8.3`_, `1.9`_ and `1.9.1`_. There was not `one`_, not `two`_, but `three`_ Tahoe-LAFS Summits. Tahoe-LAFS received a `new server`_. Numerous Tahoe-LAFS grids appeared in `Virginia Tech`_, San Franscisco (`Noisebridge`_) and location unknown (`Cryto Coding Collective`_ and `JonDonym`_). Tahoe-LAFS' influence could be seen in projects like `Nilestore`_, `FreedomBox`_, `Tamias`_ and `Cryptosphere`_. We even saw the founding of a company who donated their work back to Tahoe-LAFS, in `Least Authority Enterprise`_ (LAE) |LAE|. We are really excited in where Tahoe-LAFS is going and that "provider-independent" security is catching on all over. .. _`1.8.3`: http://tahoe-lafs.org/~marlowe/TWN14.html .. _`1.9`: http://tahoe-lafs.org/~marlowe/TWN17.html .. _`1.9.1`: http://tahoe-lafs.org/~marlowe/TWN21.html .. _`one`: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/Summit .. _`two`: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/Summit .. _`three`: https://tahoe-lafs.org/~marlowe/TWN25.html .. _`new server`: http://tahoe-lafs.org/~marlowe/TWN17.html .. _`Virginia Tech`: https://tahoe-lafs.org/~marlowe/TWN18.html .. _`Noisebridge`: http://tahoe-lafs.org/~zooko/TWN13.html .. _`Cryto Coding Collective`: https://tahoe-lafs.org/~marlowe/TWN30.html .. _`JonDonym`: http://tahoe-lafs.org/~marlowe/TWN16.html .. _`Nilestore`: http://tahoe-lafs.org/~zooko/TWN11.html .. _`FreedomBox`: http://tahoe-lafs.org/~marlowe/TWN17.html .. _`Tamias`: http://tahoe-lafs.org/~marlowe/TWN20.html .. _`Cryptosphere`: https://tahoe-lafs.org/~marlowe/TWN24.html .. _`Least Authority Enterprise`: http://tahoe-lafs.org/~marlowe/TWN15.html Thoughts from the Scribe - ------------------------ When Zooko |zooko| suggested I write a weekly Tahoe-LAFS newsletter a year ago, I was a little unsure. I was not sure what I would write about or if I would be able to provide stories which would capture the attention of the incredible community surrounding Tahoe-LAFS. I must say now that I am ever so grateful for this opportunity. I can't express my thanks enough, but I will do my very best to below. First, I would like to thank the readers. If it wasn't for you, this newsletter, wouldn't exist. Your exceptional feedback (see below) makes writing TWN a sheer joy. I look forward to doing this every week and that is in large part due to you. I would like to thank the development and support team of Tahoe-LAFS. Thank you for the gift of Tahoe-LAFS. I hope I help more people realize what a special thing we have here. In particular, I would like to thank Zooko, Brian |brian| and David-Sarah |davidsarah|. Your brilliant discussions on the mailing list and IRC stretched the limits of my brain, forcing me to look up numerous things. Thank you so much for expanding my knowledge. Thank you to Peter |peter|. Your interview helped convince me that I didn't need to be a developer to contribute to an OSS project in a meaningful way. That interview did more to encourage me to continue than you will ever know. Thanks to Kevan |kevan| for being my first interview. Thanks to Marcus |marcusw| for forwarding me all the tab completion fails :). Lastly, thanks to the many whom, I didn't get to mention. You have made me a better person and not just technically. Thank you from the bottom of my heart. Thank You to Atlas Networks - --------------------------- We would like to say thank you to `Atlas Networks`_ |AtlasNetworks| for their continued support and generous donation of four servers. As noted in `TWN #14`_, "In addition to the generosity of their hardware donation, Atlas Networks provide the Tahoe-LAFS project with remote consoles and technical support, including complete OS reinstalls." As a way of showing my appreciation, I will be moving my last VPS over to Atlas Networks. Thank you for your support. .. _Atlas Networks: http://atlasnetworks.us .. |AtlasNetworks| image:: AtlasNetworks.png :height: 35 :alt: Atlas Networks :target: http://atlasnetworks.us .. _`TWN #14`: https://tahoe-lafs.org/~marlowe/TWN14.html Redundant Array of Independent Clouds Makes a Big Splash - -------------------------------------------------------- The `article on RAIC`_ in last week's TWN made a tremendous splash. Numerous tweets regarding it appeared on Twitter. The following, "Redundant Array of Independent Clouds -- Dropbox, Googledrive, memopal, ... http://j.mp/MviO55" [`0`_] was retweeted 22 times and favorited by 41 users. Numerous other news channels picked it up and ran with the story. TWN experienced a large increase in the number of subscribers this past week. My feelings tell me it was largely a result of this story. So congratulations to Deigo "sickness" Righi |sickness|, your idea resonates with a lot of people. .. _`article on RAIC`: https://tahoe-lafs.org/~marlowe/TWN31.rst .. _`0`: https://twitter.com/newsycombinator/status/203984643253477376 Free/Open Source Project of the Week - ------------------------------------ One of the `first FOSS projects`_ we wrote about was `git-annex`. Back then, Tahoe-LAFS was made a `backend`_ to git-annex. git-annex is a tool that uses all of git's machinery for identifying and tracking files, but stores the actual complete contents of the files in a separate location instead of in the git repo itself.Now the developer, Joey Hess, is in the middle of a very ($9,842 pledged) successful `Kickstarter campaign`_. Congratulations Joey on achieving your funding and we look for to the new features which result. .. _`first FOSS projects`: https://tahoe-lafs.org/~marlowe/TWN1.html .. _`git-annex`: http://git-annex.branchable.com/ .. _`backend`: http://git-annex.branchable.com/special_remotes/ .. _`Kickstarter campaign`: http://www.kickstarter.com/projects/joeyh/git-annex-assistant-like-dropbox-… Glowing Quotes ============== Two glowing quotes this week. The first comes from a user, Saint Germain, in `response to answers to their question`_ "Wow, you guys don't do things by half... I was not expecting such a detailed answer ! After 12 years on linux, it never ceases to amaze me how open and friendly the open source community is." This last set is regarding the TWN. I would like to personally thank, j_s and Zooko for such glowing personal reviews. "whoever put together this newsletter is clearly doing a great job for that community" [`1`_] "Amen!! Patrick "marlowe" McDonald has really given us a gift by publishing the Tahoe-LAFS Weekly News every week. We're coming up on the Tahoe-LAFS Weekly News one-year anniversary next week. b:" [`2`_] .. _`response to answers to their question`: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007368.html .. _`1`: https://news.ycombinator.com/item?id=3997429 .. _`2`: https://news.ycombinator.com/item?id=3997548 Tahoe-LAFS on Twitter ===================== @SGgrc have you ever looked at Tahoe-LAFS (distributed encrypted filessytem) http://bit.ly/K26V47 [`3`_] This is awesome - a redundant, distributed file system: tahoe-lafs http://buff.ly/L7NtQM [`4`_] Here's the entry in Duplicati's blog where they announce the addition of Tahoe-LAFS backend: http://identi.ca/url/69931029 [`5`_] .. _`3`: https://twitter.com/tvgtvg/status/204143972778639360 .. _`4`: https://twitter.com/ddrager/status/204195040120143872 .. _`5`: https://twitter.com/zooko/status/205002859576705024 - From the tahoe-dev Mailing List =============================== Potential use of personal backup - -------------------------------- As mentioned above, a new user, Saint Germain was unsure of Tahoe-LAFS' ability to be used for `personal backups`_. Guido Witmond included some of the reasons to use Tahoe-LAFS for personal backup: * it's easy to setup, although not yet "Parent-proof"; * it works out-of-the-box on many platforms; * it is encrypted by default; * only you have the key, so no one else can read your data, unlike the other cloud providers; * that it shows the 'health' of your data; and allows to repair it. [`6`_] Zooko provided one of the better `descriptions of Tahoe-LAFS`_, I have experienced the privileges to read. I may have to steal it and place it in the introductory documentation. On a side note, Saint Germain is writing an article on new backup software for the French site, linuxfr.org and may add Tahoe-LAFS to the article. Regardless of whether the article includes Tahoe-LAFS, we would love to see it. .. _`personal backups`: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007349.html .. _`6`: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007350.html .. _`descriptions of Tahoe-LAFS`: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-May/007365.html Patches Needing Review of the Week ================================== There is one (1) ticket still needing review for 1.9.2: * `#1115`_: add servers-of-happiness to reports (post-repair says 10 hosts have good shares but there only 4 hosts) There are five (5) ticket still needing review for 1.10.0: * `#937`_: 'tahoe run' doesn't work for an introducer node * `#1539`_: stop putting pkg_resources.require() into .tac files * `#1159`_: stop using .tac files: make it possible to change appname, Python package-directory name, perhaps other names * `#1693`_: flogtool doesn't get automatically provided * `#1240`_: add functional test of ResponseCache in favour of MDMFSlotReadProxy's cache There are three (3) tickets still needing review of 1.11.0: * `#1265`_: New Visualizer is insufficiently labelled/documented (plus layout problem) * `#1382`_: immutable peer selection refactoring and enhancements * `#1569`_: rerecord and review pluggable backends for landing on trunk .. _`#1115`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1115 .. _`#937`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/937 .. _`#1539`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1539 .. _`#1159`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1159 .. _`#1693`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1693 .. _`#1240`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1240 .. _`#1265`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1265 .. _`#1382`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1382 .. _`#1569`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1569 - ---- *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* |marlowe| *, 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:: zooko.png :height: 35 :alt: zooko :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |peter| image:: psecor.jpg :height: 35 :alt: peter :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |marlowe| image:: marlowe-x75-bw.jpg :height: 35 :alt: marlowe :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |davidsarah| image:: davidsarah_bw.png :height: 35 :alt: davidsarah :target: http://tahoe-lafs.org/trac/tahoe-lafs/wikiAboutUs .. |brian| image:: warner.png :height: 35 :alt: brian :target: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/AboutUs .. |marcusw| image:: marcus.png :height: 35 :alt: marcusw .. |sickness| image:: sickness.jpg :height: 35 :alt: sickness .. |kevan| image:: kevan.png :height: 35 :alt: kevan .. |LAE| image:: LAE.png :height: 35 :alt: Least Authority Enterprises :target: http://leastauthority.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPw4KSAAoJEAT4nRyi0elySjIQAIcO9HPlFHdzWEKe3kAuN4ge npM99S86Iu5MiUVtc3+xA2dNEP++egISngHuiZrNYoomQbeMec3aX5VjWHr8fple wl6mhH1EJiEpBE54g6G7BlCDMrhVs53tpN0cShw7kTEtSwyjhuMtklbJaDyuxgRY V8cvarGe6l0RZf7+YWiTwl7CLVCWNXciKFMxBGCaem1iOx29TSIEMXW1Y7sVbLl7 xrK+mPdUcGM7YhLRfvnRPq8kgRBnZ9c1+Ovycp+X8/6Lvj3mu5aRndsSZDU6+tZa SdRmgIPHSNV/Cox5D1YdqSXmv+eJg+2qfH6ZPsD16QpoYoNAcBnlLaoaOn4N39Nh Yg4JASDtpLnVxJOVeSu7ROtRIJBB8ZK0E/Xfgt4C4JFR3oKVPAsqAuWhhL1qjXt8 VXf9MSu23u2AJ13CdjTw666NRRoTzf3DYodoXOJ1TWKy0QaC0gvR7z2xKxPzegAK TrvW6ksceloEOQNBRxEnRzzEqxo79GRAGywWPeR8dJq67PRo4w47nZfz/z1im12R a/T5/u24fMC8yGKbpN6QXpp7QUmJcKM+6fBYbk34pYp7eUpTmlmByogR02THt59y OAMXZlA3DRNn9HIgekcz92Bx3USNpZ2uN3yifRON48vJMR9P9nqy7awWckl1XZMw 3y7qV3YYNiP8C3fLhbl0 =WKuv -----END PGP SIGNATURE----- _______________________________________________ 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