July 2018 - cypherpunks-legacy

Re: Connectivity status for Egypt
by Alastair Johnson 06 Jul '18

06 Jul '18

On 1/28/2011 1:02 PM, Alexander Harrowell wrote: > I wonder if anyone's working on a mesh or p-t-p radio app that runs on a > smartphone? Yes - came across http://www.servalproject.org/ from the linux.conf.au program. ----- 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: Connectivity status for Egypt
by Alastair Johnson 06 Jul '18

06 Jul '18

On 1/28/2011 1:02 PM, Alexander Harrowell wrote: > I wonder if anyone's working on a mesh or p-t-p radio app that runs on a > smartphone? Yes - came across http://www.servalproject.org/ from the linux.conf.au program. ----- 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 #6
by Patrick R McDonald 06 Jul '18

06 Jul '18

===================================================== Tahoe-LAFS Weekly News, issue number 6, July 9, 2011 ===================================================== Welcome to the Tahoe-LAFS Weekly News (TWN). Tahoe-LAFS_ is a secure, distributed storage system. `View TWN on the web`_ *or* `subscribe to TWN`_. .. _Tahoe-LAFS: http://tahoe-lafs.org .. _View TWN on the web: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/TahoeLAFSWeeklyNews .. _subscribe to TWN: http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news Announcements and News ====================== Tahoe-LAFS Summit ----------------- As promised here are the updates from the Summit. Thanks to everyone who provided me notes. Once again, please enjoy the feeds by nejucomo_ and secorp. Ladies and gentleman, we have a visualizer thanks to Brian Warner. The visualizer demonstrates how encryption and hashing take significantly less time than network operations. It shows network issues which are explained (lock-step progress per-segment means higher K leads to more servers slowing each other down, redundant computation of the satisfaction algorithm leads to gaps between segments), as well as unexplained (one server has response time X, all the others have response time ~Y, Y is about an order of magnitude greater than X). Currently, the visualizer could use some usuability improvements. It is best understood with Brian explaining its functionality to you. Tahoe would greatly appreciate anyone who would like to work on 1265_ to make the visualizer more user friendly. Items needed are more labels and documents. Currently the visualizer will use a significant portion of CPU to render an image if it is asked to display all items available. Any Javascript performance experts (or others interested) who could patch it to only render visible and meaningful items will receive a write up in TWN. We discussed append-only caps. `Moxie Marlinspike`_ and Zooko want append-only caps as they are the correct security property for backups. The implementations sketched out at the Summit seem overly complicated. There are questions if append-only caps require such complication or if we could implement a simpler solution which would cover all the different threat models. The threat models include servers conspiring to rollback, someone/something compromising the capability and uncoordinated writes and/or servers being off-line. If such complication can not be removed and still cover all the threat models, should the Tahoe developers explore a simpler design which covers less threat models? Please send us your thoughts either to the `mailing list`_ or join us in #tahoe-lafs in Freenode. Peter Secor reported on Tahoe's funds. We have donations of 244.56b, received donations of about $30/month from Flattr. Thank you to all donors! We spend more than $30/month on Peter's costs to run our servers. Thanks Peter for running our servers. Josh, David-Sarah and Zooko worked on 999_. This ticket is adapting the codebase to support multiple backends including Amazon S3. There is a distinct possibility this ticket could be included in the upcoming 1.9.0 release. David-Sarah implemented Dropbox-like functionality. .. _nejucomo: http://www.ustream.tv/channel/tahoe-lafs-summit .. _secorp: http://www.ustream.tv/channel/tahoe-lafs-summit-end .. _1265: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1265 .. _`mailing list`: http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news .. _`Moxie Marlinspike`: http://www.thoughtcrime.org .. _999: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/999 Tahoe on Plug Computers ----------------------- More good news from the `FreedomBox Foundation`_. Tahoe just runs with an "apt-get install" on plug computers. .. _`FreedomBox Foundation`: http://lists.alioth.debian.org/pipermail/freedombox-discuss/2011-July/00204… Interview with the Developers ============================= There is no interview this week as well. Sorry for the delay. We will be returning to our regular interview schedule next week. Are there any questions you want me to ask the developers or a specific developer? Perhaps there is a topic and you want various developers' opinions on it. Please let me know and I will ask it here. Open Source Project of the Week =============================== The Open Source Project of the Week is FranC'ois Deppierraz's `Android client`_. This is the killer application for me for Tahoe. No longer am I tied to my laptop or my desktop to use Tahoe. I can use Tahoe wherever my cell phone can carry me. I am really looking forward to running this on my Nook Color when I root it later this year. Warning: you may be thinking that fdz's Android client is actually doing encryption on your phone. Alas, no, it is delegating that to a remote gateway running on a server. .. _`Android client`: http://github.com/ctrlaltdel/TahoeLAFS-android >From the tahoe-dev Mailing List =============================== The `DMCA discussion`_ continues. Zooko asked when `patches need to be completed`_ to be included in 1.9.0_. .. _`DMCA discussion`: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-July/006525.html .. _`patches need to be completed`: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-July/006526.html .. _1.9.0: http://tahoe-lafs.org/trac/tahoe-lafs/roadmap Patch Needing Review of the Week ================================ The Patch Needing Review of the Week is 1425_. This patch allows webapi gateway operators to block access to files natively in Tahoe rather than through of a frontend proxy (i.e. nginx, Apache). The patch creates a blacklist file, with a list of storage-index strings and a reason for each. This patch may be useful in enabling webapi gateway operators to effectively deal with DMCA complaints. .. _1425: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1425 ---- *The Tahoe-LAFS Weekly News is published once a week by The Tahoe-LAFS Software Foundation, President and Treasurer: Peter Secor. Scribes: Patrick "marlowe" McDonald, Zooko Wilcox-O'Hearn, Editor: Zooko.* `View TWN on the web`_ *or* `subscribe to TWN`_ *. Send your news stories to* marlowe(a)antagonism.org_ *b submission deadline: Friday night.* .. _marlowe(a)antagonism.org: mailto:marlowe@antagonism.org _______________________________________________ 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

paycash payment system ver. 1.xx
by Victor Dostov 06 Jul '18

06 Jul '18

Paycash, digital cash payment system, released production version 1.xx. It can be downloaded at English section of www.paycash.ru. Current pilot version has about 10,000 users what is about 1-2% of active Russian internet users. Concerning current growth rate it is expected that in the next 6 month this number will increase five times. To the moment the system has operating representative companies in Russia, Latvia, Ukraine and USA. For help on using this list (especially unsubscribing), send a message to "dcsb-request(a)reservoir.com" with one line of text: "help". --- end forwarded text -- ----------------- R. A. Hettinga <mailto: rah(a)ibuc.com> The Internet Bearer Underwriting Corporation <http://www.ibuc.com/> 44 Farquhar Street, Boston, MA 02131 USA "... however it may deserve respect for its usefulness and antiquity, [predicting the end of the world] has not been found agreeable to experience." -- Edward Gibbon, 'Decline and Fall of the Roman Empire'

1 0

web home for waste
by lgonze＠panix.com 06 Jul '18

06 Jul '18

I've gotten a bunch of queries about WASTE, generally with a focus on user problems like how to get a connection or FAQ issues like how to build on OS X. To help people to help each other, as well as to foster discussion of technical issues related to WASTE, I have created a mailing list and web home at http://groups.yahoo.com/group/waste-discuss/. - Lucas --- end forwarded text -- ----------------- R. A. Hettinga <mailto: rah(a)ibuc.com> The Internet Bearer Underwriting Corporation <http://www.ibuc.com/> 44 Farquhar Street, Boston, MA 02131 USA "... however it may deserve respect for its usefulness and antiquity, [predicting the end of the world] has not been found agreeable to experience." -- Edward Gibbon, 'Decline and Fall of the Roman Empire'

1 0

Sen.: White House Agrees to Spy Law Change
by feis 06 Jul '18

06 Jul '18

Sen.: White House Agrees to Spy Law Change By KATHERINE SHRADER, Associated Press Writer 1 hour, 35 minutes ago Senate Intelligence Chairman Pat Roberts said he has worked out an agreement with the White House to change U.S. law regarding the National Security Agency's warrantless surveillance program and provide more information about it to Congress. "We are trying to get some movement, and we have a clear indication of that movement," Roberts, R-Kan., said. Without offering specifics, Roberts said the agreement with the White House provides "a fix" to the Foreign Intelligence Surveillance Act and offers more briefings to the Senate Intelligence Committee. The deal comes as the committee was set to have a meeting Thursday about whether to open an investigation into the hotly disputed program. Roberts indicated the deal may eliminate the need for such an inquiry. Democrats have been demanding an investigation but some Republicans don't want to tangle the panel in a testy election-year probe. "Whether or not an investigation is the right thing to do at this particular time, I am not sure," Roberts told reporters while heading into the meeting. The White House was not immediately available for comment on Roberts' statement. Earlier in the day, White House spokesman Scott McClellan hinted at a "good discussion going on" with lawmakers and praised in particular "some good ideas" presented by Sen. Mike DeWine (news, bio, voting record). The Ohio Republican has suggested the FISA law be changed to accommodate the NSA program. However, McClellan left the impression that any deal would not allow for significant changes. He said the White House continued to maintain that Bush does not need Congress' approval to authorize the warrantless eavesdropping and that the president would resist any legislation that might compromise the program. "There's kind of a high bar to overcome," McClellan said. "We think there's some good ideas, but we have not seen actual legislation." Separately, the Justice Department has strongly discouraged the Senate Judiciary Committee from calling former Attorney General John Ashcroft and his deputy to testify about the surveillance program, saying they won't have new information for Congress about it. Just as Attorney General Alberto Gonzales could not talk about the administration's internal deliberations when he appeared before the committee earlier this month, neither can Ashcroft nor his former No. 2, James Comey, Assistant Attorney General William Moschella said in a letter to Senate Judiciary Committee Chairman Arlen Specter, R-Pa. The letter, written Wednesday, was obtained by The Associated Press. "In light of their inability to discuss such confidential information, along with the fact that the attorney general has already provided the executive branch position on the legal authority for the program, we do not believe that Messrs. Ashcroft and Comey would be in a position to provide any new information to the committee," Moschella wrote. He was responding to Specter's request that the two men testify this month. While Moschella indicated their testimony wouldn't be of value, he did not say the committee could not call Ashcroft and Comey to appear. The Judiciary Committee has been looking into the legality of the National Security Agency's program. In a heated daylong hearing on Feb. 6, four Republicans joined the committee's Democrats in raising questions about whether President Bush went too far in authorizing the wiretapping without court warrants. Specter wants the secretive Foreign Intelligence Surveillance Court to review the program's constitutionality. Reports have indicated that Comey and others had reservations about the program in 2004. White House Chief of Staff Andy Card and Gonzales, then the White House counsel, visited Ashcroft about those issues while Ashcroft was in the hospital for gallstone pancreatitis. ___ Associated Press Writer Mark Sherman contributed to this report. http://news.yahoo.com/s/ap/20060216/ap_on_go_co/eavesdropping_4&printer=1;_… t=A86.I2Ct.vRD4L0AqQWMwfIE;_ylu=X3oDMTA3MXN1bHE0BHNlYwN0bWE- --------------------------------------------------------------------- The Cryptography Mailing List Unsubscribe by sending "unsubscribe cryptography" to majordomo(a)metzdowd.com ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]

1 0

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

06 Jul '18

===================================================== Tahoe-LAFS Weekly News, issue number 6, July 9, 2011 ===================================================== Welcome to the Tahoe-LAFS Weekly News (TWN). Tahoe-LAFS_ is a secure, distributed storage system. `View TWN on the web`_ *or* `subscribe to TWN`_. .. _Tahoe-LAFS: http://tahoe-lafs.org .. _View TWN on the web: http://tahoe-lafs.org/trac/tahoe-lafs/wiki/TahoeLAFSWeeklyNews .. _subscribe to TWN: http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news Announcements and News ====================== Tahoe-LAFS Summit ----------------- As promised here are the updates from the Summit. Thanks to everyone who provided me notes. Once again, please enjoy the feeds by nejucomo_ and secorp. Ladies and gentleman, we have a visualizer thanks to Brian Warner. The visualizer demonstrates how encryption and hashing take significantly less time than network operations. It shows network issues which are explained (lock-step progress per-segment means higher K leads to more servers slowing each other down, redundant computation of the satisfaction algorithm leads to gaps between segments), as well as unexplained (one server has response time X, all the others have response time ~Y, Y is about an order of magnitude greater than X). Currently, the visualizer could use some usuability improvements. It is best understood with Brian explaining its functionality to you. Tahoe would greatly appreciate anyone who would like to work on 1265_ to make the visualizer more user friendly. Items needed are more labels and documents. Currently the visualizer will use a significant portion of CPU to render an image if it is asked to display all items available. Any Javascript performance experts (or others interested) who could patch it to only render visible and meaningful items will receive a write up in TWN. We discussed append-only caps. `Moxie Marlinspike`_ and Zooko want append-only caps as they are the correct security property for backups. The implementations sketched out at the Summit seem overly complicated. There are questions if append-only caps require such complication or if we could implement a simpler solution which would cover all the different threat models. The threat models include servers conspiring to rollback, someone/something compromising the capability and uncoordinated writes and/or servers being off-line. If such complication can not be removed and still cover all the threat models, should the Tahoe developers explore a simpler design which covers less threat models? Please send us your thoughts either to the `mailing list`_ or join us in #tahoe-lafs in Freenode. Peter Secor reported on Tahoe's funds. We have donations of 244.56b, received donations of about $30/month from Flattr. Thank you to all donors! We spend more than $30/month on Peter's costs to run our servers. Thanks Peter for running our servers. Josh, David-Sarah and Zooko worked on 999_. This ticket is adapting the codebase to support multiple backends including Amazon S3. There is a distinct possibility this ticket could be included in the upcoming 1.9.0 release. David-Sarah implemented Dropbox-like functionality. .. _nejucomo: http://www.ustream.tv/channel/tahoe-lafs-summit .. _secorp: http://www.ustream.tv/channel/tahoe-lafs-summit-end .. _1265: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1265 .. _`mailing list`: http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news .. _`Moxie Marlinspike`: http://www.thoughtcrime.org .. _999: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/999 Tahoe on Plug Computers ----------------------- More good news from the `FreedomBox Foundation`_. Tahoe just runs with an "apt-get install" on plug computers. .. _`FreedomBox Foundation`: http://lists.alioth.debian.org/pipermail/freedombox-discuss/2011-July/00204… Interview with the Developers ============================= There is no interview this week as well. Sorry for the delay. We will be returning to our regular interview schedule next week. Are there any questions you want me to ask the developers or a specific developer? Perhaps there is a topic and you want various developers' opinions on it. Please let me know and I will ask it here. Open Source Project of the Week =============================== The Open Source Project of the Week is FranC'ois Deppierraz's `Android client`_. This is the killer application for me for Tahoe. No longer am I tied to my laptop or my desktop to use Tahoe. I can use Tahoe wherever my cell phone can carry me. I am really looking forward to running this on my Nook Color when I root it later this year. Warning: you may be thinking that fdz's Android client is actually doing encryption on your phone. Alas, no, it is delegating that to a remote gateway running on a server. .. _`Android client`: http://github.com/ctrlaltdel/TahoeLAFS-android >From the tahoe-dev Mailing List =============================== The `DMCA discussion`_ continues. Zooko asked when `patches need to be completed`_ to be included in 1.9.0_. .. _`DMCA discussion`: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-July/006525.html .. _`patches need to be completed`: http://tahoe-lafs.org/pipermail/tahoe-dev/2011-July/006526.html .. _1.9.0: http://tahoe-lafs.org/trac/tahoe-lafs/roadmap Patch Needing Review of the Week ================================ The Patch Needing Review of the Week is 1425_. This patch allows webapi gateway operators to block access to files natively in Tahoe rather than through of a frontend proxy (i.e. nginx, Apache). The patch creates a blacklist file, with a list of storage-index strings and a reason for each. This patch may be useful in enabling webapi gateway operators to effectively deal with DMCA complaints. .. _1425: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1425 ---- *The Tahoe-LAFS Weekly News is published once a week by The Tahoe-LAFS Software Foundation, President and Treasurer: Peter Secor. Scribes: Patrick "marlowe" McDonald, Zooko Wilcox-O'Hearn, Editor: Zooko.* `View TWN on the web`_ *or* `subscribe to TWN`_ *. Send your news stories to* marlowe(a)antagonism.org_ *b submission deadline: Friday night.* .. _marlowe(a)antagonism.org: mailto:marlowe@antagonism.org _______________________________________________ tahoe-lafs-weekly-news mailing list tahoe-lafs-weekly-news(a)tahoe-lafs.org http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-weekly-news ----- End forwarded message ----- -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE

1 0

None
by None 06 Jul '18

06 Jul '18

Last night, Serge Mister and Robert Zuccherato published a paper reporting on an attack against OpenPGP symmetric encryption. This attack, while very significant from a cryptographic point of view, is not generally effective in the real world. To be specific, unless you have your OpenPGP program set up as part of an automated system to accept encrypted messages, decrypt them, and then provide a response to the submitter, then this does not affect you at all. There is a very good writeup on the attack that goes into more depth at http://www.pgp.com/library/ctocorner/openpgp.html There will undoubtedly be further discussion of this over the next several days, but I wanted to provide a few comments now, to try and answer some questions that may arise: 1) This is not a bug in any particular OpenPGP implementation (GnuPG, PGP, Hushmail, etc). Rather, this is an attack against the OpenPGP protocol itself. 2) The attack requires an average of 32,768 probes to get two bytes of plaintext. This is why it is completely ineffective against human beings, who will presumably wonder why a stranger wants them to decrypt thousands and thousands of messages that won't decrypt, and then tell them what errors were seen. 3) It might be effective against an automated process that incorporates OpenPGP decryption, if that process returns errors back to the sender. 4) The OpenPGP Working Group will be discussing this issue and coming up with an effective and permanent fix. In the meantime, I have attached two patches to this mail. These patches disable a portion of the OpenPGP protocol that the attack is exploiting. This change should not be user visible. With the patch in place, this attack will not work using a public-key encrypted message. It will still work using a passphrase-encrypted message. These patches will be part of the 1.2.8 and 1.4.1 releases of GnuPG. 5) The full paper is available at http://eprint.iacr.org/2005/033 It's a great piece of work. David _______________________________________________ Gnupg-announce mailing list Gnupg-announce(a)gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce --- end forwarded text -- ----------------- R. A. Hettinga <mailto: rah(a)ibuc.com> The Internet Bearer Underwriting Corporation <http://www.ibuc.com/> 44 Farquhar Street, Boston, MA 02131 USA "... however it may deserve respect for its usefulness and antiquity, [predicting the end of the world] has not been found agreeable to experience." -- Edward Gibbon, 'Decline and Fall of the Roman Empire'

1 0

None
by None 06 Jul '18

06 Jul '18

Last night, Serge Mister and Robert Zuccherato published a paper reporting on an attack against OpenPGP symmetric encryption. This attack, while very significant from a cryptographic point of view, is not generally effective in the real world. To be specific, unless you have your OpenPGP program set up as part of an automated system to accept encrypted messages, decrypt them, and then provide a response to the submitter, then this does not affect you at all. There is a very good writeup on the attack that goes into more depth at http://www.pgp.com/library/ctocorner/openpgp.html There will undoubtedly be further discussion of this over the next several days, but I wanted to provide a few comments now, to try and answer some questions that may arise: 1) This is not a bug in any particular OpenPGP implementation (GnuPG, PGP, Hushmail, etc). Rather, this is an attack against the OpenPGP protocol itself. 2) The attack requires an average of 32,768 probes to get two bytes of plaintext. This is why it is completely ineffective against human beings, who will presumably wonder why a stranger wants them to decrypt thousands and thousands of messages that won't decrypt, and then tell them what errors were seen. 3) It might be effective against an automated process that incorporates OpenPGP decryption, if that process returns errors back to the sender. 4) The OpenPGP Working Group will be discussing this issue and coming up with an effective and permanent fix. In the meantime, I have attached two patches to this mail. These patches disable a portion of the OpenPGP protocol that the attack is exploiting. This change should not be user visible. With the patch in place, this attack will not work using a public-key encrypted message. It will still work using a passphrase-encrypted message. These patches will be part of the 1.2.8 and 1.4.1 releases of GnuPG. 5) The full paper is available at http://eprint.iacr.org/2005/033 It's a great piece of work. David _______________________________________________ Gnupg-announce mailing list Gnupg-announce(a)gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce --- end forwarded text -- ----------------- R. A. Hettinga <mailto: rah(a)ibuc.com> The Internet Bearer Underwriting Corporation <http://www.ibuc.com/> 44 Farquhar Street, Boston, MA 02131 USA "... however it may deserve respect for its usefulness and antiquity, [predicting the end of the world] has not been found agreeable to experience." -- Edward Gibbon, 'Decline and Fall of the Roman Empire'

1 0

None
by None 06 Jul '18

06 Jul '18

Last night, Serge Mister and Robert Zuccherato published a paper reporting on an attack against OpenPGP symmetric encryption. This attack, while very significant from a cryptographic point of view, is not generally effective in the real world. To be specific, unless you have your OpenPGP program set up as part of an automated system to accept encrypted messages, decrypt them, and then provide a response to the submitter, then this does not affect you at all. There is a very good writeup on the attack that goes into more depth at http://www.pgp.com/library/ctocorner/openpgp.html There will undoubtedly be further discussion of this over the next several days, but I wanted to provide a few comments now, to try and answer some questions that may arise: 1) This is not a bug in any particular OpenPGP implementation (GnuPG, PGP, Hushmail, etc). Rather, this is an attack against the OpenPGP protocol itself. 2) The attack requires an average of 32,768 probes to get two bytes of plaintext. This is why it is completely ineffective against human beings, who will presumably wonder why a stranger wants them to decrypt thousands and thousands of messages that won't decrypt, and then tell them what errors were seen. 3) It might be effective against an automated process that incorporates OpenPGP decryption, if that process returns errors back to the sender. 4) The OpenPGP Working Group will be discussing this issue and coming up with an effective and permanent fix. In the meantime, I have attached two patches to this mail. These patches disable a portion of the OpenPGP protocol that the attack is exploiting. This change should not be user visible. With the patch in place, this attack will not work using a public-key encrypted message. It will still work using a passphrase-encrypted message. These patches will be part of the 1.2.8 and 1.4.1 releases of GnuPG. 5) The full paper is available at http://eprint.iacr.org/2005/033 It's a great piece of work. David _______________________________________________ Gnupg-announce mailing list Gnupg-announce(a)gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce --- end forwarded text -- ----------------- R. A. Hettinga <mailto: rah(a)ibuc.com> The Internet Bearer Underwriting Corporation <http://www.ibuc.com/> 44 Farquhar Street, Boston, MA 02131 USA "... however it may deserve respect for its usefulness and antiquity, [predicting the end of the world] has not been found agreeable to experience." -- Edward Gibbon, 'Decline and Fall of the Roman Empire'

1 0