February 2014 - cypherpunks@lists.ogf.org

A Surprisingly Easy Tool for Encrypting Email, Courtesy of an Ex-NSA Employee
by Gutem 10 Mar '14

10 Mar '14

Encrypting for the masses? http://motherboard.vice.com/blog/a-surprisingly-easy-tool-for-encrypting-em… Att, - Gutem ------------------------------------------------------------------------------------------- Registered Linux User: 562142

5 4

Inferring the NSA's MO from a short clip of Joel Brenner on BBC
by Jen Savage 10 Mar '14

10 Mar '14

I want to preface this message with a disclaimer: I am in no way defending the actions of the NSA. I am merely attempting analysis of their motivations and their MO. https://www.youtube.com/watch?v=H33r2weM6Zc Joel Brenner says, "There is in all the intelligence agencies a tension between doing offense better and doing defense better" ...and, "but unless you think 0days are finite" Ok let's talk about this issue for a moment. - In the CTF world, it has been widely accepted that given a red team and a blue team of equal abilities, the red team always wins. - Academics say there is no way to create provably secure software. - Developers have a phrase, "there is no such thing as bug free software." - CISOs are using the term "risk" to describe pen test findings: a recognition that pen tests have become a measure of the risk that someone will find an exploitable flaw. Suppose that the NSA gave up on securing software because they view it as impossible. In fact, we know they view it as impossible because they have called it a Sisyphean Task. If there are diminishing returns from reporting software vulnerabilities to the vendor, then doing so is a losing battle. I hear people say that the NSA undermines the security of software by not releasing the vulnerabilities, but we know that historically companies have been very bad at actually fixing the vulnerabilities they are given. In some cases, a new product is released before a vulnerability is even looked into, thus rendering the effort useless. So, is defense dead? Is that an accepted fact these days? If offense is a type of defense, is the NSA perhaps aiming to use 0day for their offensive capabilities to effect a kind of defense? How would they accomplish this? Have any of you been to the Berlin Unterwelten? It is a tour of revision after revision of nuclear bomb shelters that could never possibly save the population they are tasked with saving. We are living in an age where there is an entire set of strategies that deal with war in a world with weapons so strong that no walls can possibly defend against them. Although the reach of nuclear weapons historically has been further reaching than so-called "cyber" weapons, that is changing. Despite the very many warnings from the infosec industry, that is changing. (Sometimes I think my Home Invasion 2.0 talk fell on deaf ears because smart home appliances are proliferating.) And in the future of smart homes, smart cities, even smart bodies, when everything is internet connected: everyone is vulnerable. Imagine cities that can be invaded without physical armies. If you were the NSA, and you believed these things to be true, what would you be doing? -Jen

3 2

Get offa my lawn. (was Re: [Cryptography] BitCoin bug reported)
by Robert Hettinga 10 Mar '14

10 Mar '14

On Feb 16, 2014, at 10:40 PM, Lucky Green <shamrock(a)cypherpunks.to> wrote: > I say, let them and all of Bitcoin burn to dust. Dang kids. Get offa my lawn. It’s been interesting, I’ll say that much. I have people on their honeymoon here in .ai asking to see me, buy me and Mrs. RAH $30 hamburgers at Viceroy, etc. Or “prove”, “stylometrically", on various Bitcoin fora, that I'm Satoshi. Heh. I’ll never get tired of braggin’ about *that* one. :-) I expect others here know where the stylistic clues came from, but I think Grigg has the right approach to that question. Leave well enough alone. Being, even now, generally optimistic about the future, if not my own in particular, I can’t help thinking there’s a pony in there somewhere. I *do* find it annoying that the only time people wanna talk to me about this stuff is at the top of a bubble. I expect that it may be a hint from the Almighty I should pay attention to. At the moment, PayPal, which we all looked down the nose at back then, is still, um, printing money, and a cypherpunk gave me some BTC a little while ago, a kind of eating-the-dog food exercise for old time’s sake. Or something. The price has since fallen 40%, but it’s bouncing back, and will probably be fine. “You have to be *this* tall to take this ride”, as another friend said about Bitcoin prices last week. Meanwhile I can’t think of anything I want to spend it on anyway. Even in its current form, Bitcoin makes rather short work of those speed bumps Mr. May used to tell us about, which *may* be the real point to the exercise. Having to file several kinds of forms to get paid for a small consulting job as US citizen outside the US was enough to make me foreswear getting paid for much of anything anymore, anything small at least, and BTC solves several problems there quite handily, push ever came to shove. Besides, my passport is stamped “Employment Prohibited”, which, apparently, I’m evidently honoring even in the breach. So, I think BTC, or something like it, would make a nice numeraire, temporary or otherwise, having gnawed at the edges of *that* problem when most of the Bitcoinners were, as Marc notes, in short-pants. Yes, even in its current volatile state. And contrary to the opinions of people who know better than I do about these things. It wasn't quite what Dr. Fama got the Nobel for, but New Monetary Economics might be as good once as it ever was, and Bitcoin might be the camel’s nose under that particular tent, and given that it is the ultimate fiat currency that’s quite an assertion. As someone whose stated goal, back in the day, was to securitize *everything*, debt, equity, cash, services, title to assets in storage, transit, or just sitting there with a house on it, cats, dogs, mass hysteria -- and all derivatives thereof -- using bearer-transaction financial cryptography protocols on a ubiquitous geodesic public internetwork, Bitcoin *is* a bit, oh, please let me say it, self-referent as a solution. I saw it blow by here on this list, said, “meh”, shortly had the magic smoke go out of most of my internet presence by a power-spike in a hurricane, and never got around to paying attention to either Bitcoin, or the internet, very much at all until various people frog-marched my attention back into focus recently with me muttering variously about being too old for this shit anymore... So, Bitcoin, if it survives, makes a *nice* hack, by solving, what Barnes, and ultimately everyone else, called the “loading problem”. And, so far at least, it solves the “and then you go to jail” part of the book-entry transaction error-handler, something Barnes was also noted for saying. That, too, only if Bitcoin survives. "...any [network] architecture that can survive a nuclear attack can survive withdrawal of government subsidy...” Godwin said on Cyberia, long ago. I’ve jokingly called it his Second Law. I suppose the Strong Form of that hypothesis, speaking of Dr. Fama, is surviving not mere withdrawal of the implicit subsidy of monopolistic contract enforcement, and all transfer-priced assets and “externalities” appertaining thereto, but also active attack from the ostensible contract enforcer itself. I hear of others, well, gnawing around the edges, actually, of securitizing other stuff with variants of the Bitcoin protocol, but, like predicting the end of the world, expanding the blockchain to other assets "has not been found agreeable to experience.” So far as I can see. Meanwhile, Chris Odom, aka, “Fellow Traveller”, aka, “Lovedrop” (yes, *that* “Lovedrop”), is banging away on something called Open Transactions, which inserts an actual transaction protocol, among other much more interesting things, into the works to glue Bitcoin and other stuff onto, for starters, Wagner Blinding, using, for starters, Ben Laurie’s lucre code. I haven’t seen a code-stoke like the one I see Chris with, well, since the old days. Which is nice. Very nice. Big grins all around, down here in the elbow of the Caribbean. Apparently, like me, he noticed that he was delivering instantly-usable product now, and getting paid later, too much later usually. I discovered cypherpunks in late spring of 1994 looking for a solution to something Barnes (again) called the “latency” problem. Chriss bumped into the gold-silver-crypto list, I think, about 10 years later. Mr. Odom has been been kind enough to involve me in testing OT a bit, and, ultimately, I’ve more-or-less bailed on iterative break-it-and-fix-it. Mostly because I don’t have the patience for testing — much less writing — code, if I ever really did. But here’s the rub, I also I have no *idea* what I, personally, would do with Open Transactions these days even if I could get it running in production. I have lots of ideas in *general*, you understand, but they’re mostly of the “let’s you and him fight” variety. Many more people than *I* would have to be involved, they, and I, would risk much more than money, and, ultimately, I’m not sure any of it would work. It’s a drag to think that most of what I’m interested in doing requires the dissolution, or at least dissipation, of The World’s Only Remaining Superpower to happen. As someone who still, barely, calls himself mostly an anarcho-capitalist but still a patriot, that’s about the only thing worse than only being interesting to other people during the top of a bubble. Yup. A Mass of Contradictions, as usual. "Let’s you and him fight" is only two or three steps removed from Mr. Briceno’s original observation, I figure. Hell, even “set here next to the rockin' chair, sonny, and I’ll tell ya a story”, is, ultimately, not much more help than “get off my lawn”, when you get right down to it... Cheers, RAH

2 2

CIA Project CHAOS/MHCHAOS
by Gregory Foster 10 Mar '14

10 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Document Exploitation (Feb 26) - "Confirmed: The CIA Destroyed Its Noam Chomsky File and Thousands More on Other U.S. Citizens": http://www.docexblog.com/2014/02/confirmed-cia-destroyed-its-noam.html > The file [scheduled for destruction] contains 7840 of a total of > 8,328 folders on individual U.S. persons (citizens, resident > aliens) and 2,196 volumes consisting of official and "soft" subject > files and so-called sensitive files (i.e., > organizations/activities), individual documents, and the index > related to these collections which were established under project > CHAOS during the period 1967-1974. The files were opened to > maintain information bearing on possible foreign Communist > exploitation of dissention in the United States, primarily > concerning the Vietnam War. Subjects of the folders were U.S. > citizens and organizations involved in dissident activities in the > United States. Now about that alleged CIA/FBI line between foreign and domestic surveillance... Also interesting as a historical precedent for why the NSA should be required to retain records in its databases which otherwise would be (allegedly) automatically purged on schedule: they are evidence of crimes helpful for active lawsuits. https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CCgQqQ… HT the invaluable @saftergood, gf - -- Gregory Foster || gfoster(a)entersection.org @gregoryfoster <> http://entersection.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org iQIcBAEBCgAGBQJTDrP6AAoJEMaAACmjGtgj2IsP/1P4Xc/ZBmm7TImxGrsVxjJQ Nu0HU+YltOAS68NbDfCKo/yQhYnDkvbjjuEO6WiTmEtf9C6sr1f0Xitr2n7PZEft BC397hkp02i8xZGeny5dn3JENe/8DNromdGfO+v5/oQ3ZNURNX+S8aIWxAVHL2ws ebxuR5CrlWFFhbg9H9YAMDe0DtXc54vWoEXC36rEpvKLpTWC5LZl8QuikbtuIC9m xW8LhwQMKUDT/mZFQ+W0W6KAFWlWHMEWRC2mEL2aKucbf2rfND7FX/pgYyeRjUeF iLrI8orHqJKDtddeFNO0agTz21v2+4D88hFk/4FjRdrUAFNHcAy7XrF9zwDP/Kzm jqcWFIFjEbPTDxRR4tXlA5aMnkqose+N77LRXk4YKACgfmK+cPaYkVaPCgJ4D7uO pOZSRnduRkdI6VPdvVww8AvHYGhkbwDUBGc7CQN1WMiBtyLSHsnji7stxDsIMVze ervt8ZkjGWJWT/BgFsJYUE/MH8TCMd0m3y2jmQG9nVwyYURCz8fn+AiOMgv2rynB +aSA6SqCQiXKpAT6GGbRvijUmmVY9Bx3jUzqh72jGp3ANRq53E+ySS4z6TPXe3e5 P6QvCvNegnTEhdgy4zc5Q9buwdShQEZRVC/7YetmodloT3czjBX3me/nTGvpFxwy jAoQVJ2hSDA1L5jCBLyI =L5rJ -----END PGP SIGNATURE-----

2 1

Test #1
by Cypher 10 Mar '14

10 Mar '14

This is a test to validate if I am properly receiving list email. I've not seen anything in a few days. Cypher

8 9

Red Pike cipher
by Anonymous Remailer (austria) 10 Mar '14

10 Mar '14

/* Red Pike cipher source code */ #include <stdint.h> typedef uint32_t word; #define CONST 0x9E3779B9 #define ROUNDS 16 #define ROTL(X, R) (((X) << ((R) & 31)) | ((X) >> (32 - ((R) & 31)))) #define ROTR(X, R) (((X) >> ((R) & 31)) | ((X) << (32 - ((R) & 31)))) void encrypt(word * x, const word * k) { unsigned int i; word rk0 = k[0]; word rk1 = k[1]; for (i = 0; i < ROUNDS; i++) { rk0 += CONST; rk1 -= CONST; x[0] ^= rk0; x[0] += x[1]; x[0] = ROTL(x[0], x[1]); x[1] = ROTR(x[1], x[0]); x[1] -= x[0]; x[1] ^= rk1; } rk0 = x[0]; x[0] = x[1]; x[1] = rk0; } void decrypt(word * x, const word * k) { word dk[2] = { k[1] - CONST * (ROUNDS + 1), k[0] + CONST * (ROUNDS + 1) }; encrypt(x, dk); }

5 5

time to set up the test amplifier script again :)
by Anonymous Remailer (austria) 01 Mar '14

01 Mar '14

damn bunch of fucking luddites.. whine piss and moan about test test test?? I will set up and run my "test amplifier" procmail script from the 1990's just for fucking with the whiners heads! fucking software wimps the "MEDUSA" tentacle #99 ps been way too fucking quiet around here fuckwads are all at the RSA conference selling us out!

2 1

TEST TEST TEST MOTHERFUCKER!!!
by Anonymous Remailer (austria) 01 Mar '14

01 Mar '14

test... got an objection to test? improve your fucking spam filters you fucking idiots

5 5

Gox
by Rich Jones 28 Feb '14

28 Feb '14

Alleged leaked doc from inside Mt. Gox: http://www.scribd.com/doc/209050732/MtGox-Situation-Crisis-Strategy-Draft Nasty lookin', especially that assets and liabilities page! Although I don't understand how the theft could affect their cold storage. Soooooo.. who got burned? R

11 23

Whonix Anonymous Operating System Version 8 Released!
by Griffin Boyce 27 Feb '14

27 Feb '14

-------- Original Message -------- Subject: [tor-talk] Whonix Anonymous Operating System Version 8 Released! Date: Thu, 27 Feb 2014 22:06:23 +0000 From: Patrick Schleizer <adrelanos(a)riseup.net> Reply-To: tor-talk(a)lists.torproject.org To: tor-talk(a)lists.torproject.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Whonix is an operating system focused on anonymity, privacy and security. It's based on the Tor anonymity network, Debian GNU/Linux and security by isolation. DNS leaks are impossible, and not even malware with root privileges can find out the user's real IP. Whonix consists of two parts: One solely runs Tor and acts as a gateway, which we call Whonix-Gateway. The other, which we call Whonix-Workstation, is on a completely isolated network. Only connections through Tor are possible. Download Whonix for VirtualBox ############################## https://www.whonix.org/wiki/Download Download Whonxi for KVM / Qemu ############################## Experimental. See below. Users of Whonix 7 and below ########################### There is no upgrade path from Whonix 7 to Whonix 8, sorry. You have to manually download new Whonix images. Call for Help ############# - - If you know shell scripting (/bin/bash) and linux sysadmin, please join us! There are plenty of ways to make Whonix safer. - - We are also looking for a download mirros. - - For https://www.whonix.org we need some help with css, html, mediawiki, wordpress, webdesign. Download Whonix for KVM / Qemu ############################## Entirely untested! This is only useful if you have a developers mindset! This is the first time .qcow2 images are available (as .tar.gz, qcow2 image must be unpacked): http://sourceforge.net/projects/whonix/files/current/8/ We have unfinished(!) instructions for KVM: https://www.whonix.org/wiki/KVM There are still a few blockers before using Whonix with KVM can be considered sane: https://www.whonix.org/wiki/Dev/KVM Please help out solving them. Whonix also needs a maintainer to support using Whonix with KVM. If you want to upgrade existing Whonix version using Whonix's APT repository ################################################################ Sorry, upgrading from existing Whonix version (0.5.6, 7, etc.) to Whonix 8 is not be possible. Updating from the previous testers-only version 7.7.8.6 or 7.7.9.8 should be possible when you have Whonix's (stable) APT repository enabled. See: https://www.whonix.org/wiki/Whonix-APT-Repository (Whonix 7.7.9.8 is the same version as Whonix 8, just a different version number.) If you want to upgrade existing Whonix version from source code ############################################################### Sorry, upgrading from existing Whonix version (0.5.6, 7, etc.) to Whonix 8 is not be possible. Updating from the previous testers-only version 7.7.8.6 or 7.7.9.8 should be possible, see: https://www.whonix.org/wiki/Dev/BuildDocumentation_8_deb (Whonix 7.7.9.8 is the same version as Whonix 8, just a different version number.) If you want to build images from source code ############################################ See https://www.whonix.org/wiki/Dev/BuildDocumentation. Physical Isolation users ######################## See https://www.whonix.org/wiki/Physical_Isolation. Changelog between Whonix 7 and Whonix 8 ####################################### * Whonix is now based on Debian stable instead of Debian testing. * In new installations, automatic updates of Whonix's debian packages are disabled by default. During first start, users can decide if they want to enable Whonix's APT repository or want to leave it disabled. * Fixed Whonix's Tor Browser download and start script for TBB 3.5. * Fixed physical isolation build script. * Verifiable Builds. Whonix now has a feature which allows the community to check that Whonix .ova releases are verifiably created from project's own source code. Also made ade Whonix's APT repository verifiable (even deterministic!). Please see https://www.whonix.org/wiki/Verifiable_Builds for details. * Made Whonix build script configurable (can now build terminal-only Whonix-Gateway's and/or Whonix-Workstations; 64 bit builds and more) * Improved Whonix News's security. All Whonix News Files are now inside one tarball, which is signed. This stops leaking how many users are using a particular version. * whonixcheck's Whonix News download now checks if Whonix News are still valid (currently up to 4 weeks) and therefore detects indefinite freeze and replay attacks. * whonix_repository tool now has a graphical user interface; added more command line switches. * Set default locale to en_US.UTF-8. * Simplified custom user installation of TorChat, thanks to dummytor. (Protecting from Tor over Tor.) * Removed apper and synaptic from default installation, because they are too confusing / have too many bugs, do not always work in all cases for all users, #104, can still be manually installed if wanted, see also https://www.whonix.org/wiki/Dev/Automatic_Updates * whonixcheck: more configuration options, any function can now be disabled, this is useful for users who wish to disable control port filter proxy, they can disable the check_tor_bootstrap function * whonixcheck: added protection against possibly malicious strings from check.torproject.org (in case of a bug, compromise of check.tpo server or CA compromise), IP strings are now max 50 characters long. User will be warned in case the limit is exceeded. * Whonix-Workstation: no longer installing Tor Browser by default, this simplified implementing verifiable builds (#113), installing iceweasel by default, which can be used to download Tor Browser, added local iceweasel browser homepage saying that iceweasel should not be used for anything other than downloading Tor Browser, unless one knows what one is doing. * Removed galternatives from whonix-workstation-default-applications because galternatives has been (temporarily) removed from Debian testing * Building Whonix from frozen repository, from snapshot.debian.org to make the build script more resistant from upstream changes and also to make Whonix verifiable. * The Whonix Team can now use separate keys for Whonix's APT Repository and Whonix News. * Added technical documentation about keys in Whonix whonix_shared/usr/share/whonix/keys/readme. * new man page: man/whonix_shared/sdwdate.8.ronn * Deactivated Maximizing Windows by dragging them to the top of the screen to prevent users from accidentally maximizing their browser window when they are using resolutions higher than 1024x768. See https://www.whonix.org/wiki/Higher_Screen_Resolution ; https://github.com/Whonix/Whonix/issues/110 and https://trac.torproject.org/projects/tor/ticket/7255 for more information. #108 * added udisks to whonix-shared-packages-recommended for mounting removable drives * KDE settings changes, set to oxygen as suggested by scarp in "[Whonix-devel] Plastique kwin style & Widget Style" * whonixcheck: increased timeout for the tor bootstrap.py utility from 5 to 10 seconds to make it compatible with slow systems as per bug reporthttps://www.whonix.org/wiki/Special:AWCforum/st/id248/whonixcheck%3A_… * whonixcheck: Whonix News File is now deterministic * whonixcheck: Whonix News added timeout for gpg and tar * added secure-delete, because it contains sfill, which can be used to zero out free space, which is required for disk shrinking * Deactivated running update-command-not-found during build, since not deterministic (verifiable). Manually running is of course still possible. * whonix_shared/etc/apt/sources.list.d/torproject.list: removed the "deb http://deb.torproject.org/torproject.org tor-0.2.4.x-jessie main" repository, since that repository has been removed by The Tor Project (Tor is now in their Debian testing repository, which is already added) * fixed a bug reported by scarp, whonix_shared/usr/share/whonix/postinst.d/70_disable_kdm_autostart: was not disabling other display managers other than kdm. Now using the more generic /usr/lib/whonix/display-manager-dpkg-post-invoke. * msgcollector: fix race condition not always closing progress bar when it reached 100% * Whonix-Gateway: Workaround for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732578 https://www.whonix.org/wiki/Download#Connection_Issues_-_Tor_stops_working_… https://www.whonix.org/wiki/Special:AWCforum/st/id287/new_tor_and_debian_up… Set in /etc/default/tor: USE_AA_EXEC="no" Can be commented out when that bug gets fixed. * optionally (opt-in) building qcow2 images, first rudimentary implementation, build target (VirtualBox or qcow2 or both) should probably be configurable in whonix_build script (#122) * Whonix News Blog Download / Whonix News: Whonix News Blogs (Whonix Feature Blog and Whonix Important Blog) are now deployed over the same mechanism as Whonix News. * Whonix-Workstation: better implementation of dummytor using config-package-dev (might break compatibility with Whonix 7) * removed adrelanos' old key; removed whonix_shared/usr/share/whonix/postinst.d/70_legacy (breaks compatiblity with Whonix 7) * Re-implemented uwt and dummytor using config-package-dev instead of custom dpkg-diversions. Breaks compatibly with Whonix 7. * Removed rawdog and pandoc since no longer required. * moved misc scripts (Scripts for managing Whonix's offical repository and Whonix News; debug scripts; developer documentation and deprecated code) to https://github.com/Whonix/whonix-developer-meta-files * whonixcheck: do not show output of gpg for Whonix News verification * whonixcheck: do not start whonixcheck, if whonixsetup hasn't finished yet * whonixcheck: new --verbose / --debug options * whonixcheck: Check that /proc/sys/net/ipv4/ip_forward and /proc/sys/net/ipv6/ip_forward aren't set to 1 to prevent users from shooting their own feet. * whonixcheck: Whonix News can now optionally be signed with two keys, as long as either one is still valid, will be accepted * whonixcheck: whonix_shared/etc/init.d/whonixcheckd: on stop, give whonixcheck time to gracefully shut down so it can close any still eventually open progress bars * whonixcheck: fix, exit cleanly (close progress bar) when killed by other instance of whonixcheck * whonixsetup: start whonixcheck at the end of whonixsetup on Whonix-Workstation * torbrowser: hide output of gpg import; ask "Start Tor Browser yes/no" after upgrading" * torbrowser: added timeout to gpg to prevent endless data attacks * torbrowser/whonixcheck: alternative method detecting locally installed Tor Browser version. When $tbb_folder/Docs/version does not exist, i.e. when the user manually downloaded Tor Browser, try to detect version number from ~/tor-browser_en-US/Docs/sources/versions.; comment * desktop: higher resolution icons for whonix_repository, whonixcheck, contribute and donate, whonix gateway firewall, tb recommend, important blog and torbrowser * ram adjusted desktop starter: fixed lightdm (/usr/sbin/...) auto detection * qcow2 images: added metadata preallocation * qcow2 images: added "-o cluster_size=2M" to "qemu-img" for better performance * build script: fix "sudo: unable to resolve host debian" * build script: added --no-options to gpg to avoid conflict with user's gpg config files * build script: added benchmarking * build script: whonix_build_both: support extra parameter * build script: got rid of grml_config by using grml-debootstrap's new environment variables feature * build script: skip backup-img-after-grml-debootstrap and backup-img-after-meta-package-install build steps by default, can be re-enabled by builder * build script: allow running build-steps.d/2400_convert-img-to-qcow2 without root * build script: improved error handling, when error is detected, wait until builder presses enter before cleanup and exit to make it simpler to read error messages when building in cli * build script: fixed update-locale bug build script: Avoiding "perl: warning: Setting locale failed." as suggested on https://wiki.ubuntu.com/DebootstrapChroot and https://lists.debian.org/debian-amd64/2005/08/msg00249.html by setting export LANG="C" * verifiable builds: new build step build-steps.d/2350_cleanup; Get rid of /dev folder inside the vm image. This is only required for verifiable builds. Otherwise this could be skipped. For example, "sudo sha512sum /dev/xconsole" or "sudo sha512sum /dev/initctl" would run forever. The /dev folder gets recreated by the kernel upon first boot. * Improved messages. * Lots of smaller fixes. * Code refactoring. * For more details, see the git log. -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJTD7beXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2RTk3OUIyOEE2RjM3QzQzQkUzMEFGQTFD QjhENTBCQjc3QkIzQzQ4AAoJEMuNULt3uzxIU9oP/22e7sqG07qwTywxpfA0UVX/ QLtJ5i4KBJIoJUk7VWgt63r6dFlFkWIWD5EGn/CC4OywS/9DPNHA+lgrzJQdSZe2 NduB2cSihcewkxI2Mjb1X+VFcw3okzAokDrZ9EMblWHKjhlunBeoQmfGj9oCKc4p LCebZChFF0vAebk71hBMVcafgQEciHKx4KJKUsJQ+Dmhcbfa3Elba5QM5wKw6Whh DlqRUJ0UM+x/SQ/3dwIE5vMWdf1tj11q6P7BeJN7XUWf68FX0f1Zy/r8JtWwEt8q 5ZN9JXcGO/SAZdzFUvrhMCj93l/uBzTeC595mqLOkP8d700ofg1dVOnDdy1eiwh9 /uGJ+H7983te90WnkHnu8NTBfqwfi/ZmNNR+LBnNVxBUywXQaaUWCTgdHCx59CI9 hs9Wl5wxNLmeRbBvRCCbjNSir+1wbtKCeSb8NTBrsWOqyN/tIioN4vnoA33ls5tq HYxFNdMkaLAsSb6pO/b9oIs2EeXUL8t/E1mc9Jr3H7nkm5FbE+9sClugod+PPXL8 RiGU0o/XiVU/aaT+7iVAaTF7z8wlXFTTsQ1V6/FgsRAAVy9dKJQriPTY+bPcJhLZ 1z+VaTRcxXA+rCSM9VeBBYg1lzFevJP7ExH5y6cFgE8DBLPUtXG5cCISGZFS0A0x NzmZy2053AFzuPNAu5WC =JQiF -----END PGP SIGNATURE----- -- tor-talk mailing list - tor-talk(a)lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

1 0