From 046f8de140509033bdd33b1bcfc22dcc3b52dd47 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawmkBwMWvNKZZCge_YqobCSILPMeK6xbFw8" Date: Thu, 2 May 2013 17:13:29 +0000 Subject: [PATCH] --- ..._goes_to_100__37___cpu_on_bad_input_data.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/gpg_goes_to_100__37___cpu_on_bad_input_data.mdwn diff --git a/doc/bugs/gpg_goes_to_100__37___cpu_on_bad_input_data.mdwn b/doc/bugs/gpg_goes_to_100__37___cpu_on_bad_input_data.mdwn new file mode 100644 index 0000000000..d86c82d37a --- /dev/null +++ b/doc/bugs/gpg_goes_to_100__37___cpu_on_bad_input_data.mdwn @@ -0,0 +1,16 @@ +### Please describe the problem. +Bad input data given to gpg will make it lock. + +### What steps will reproduce the problem? +Trying to download gpg encrypted data from remote with bad/incorrect dat + +### What version of git-annex are you using? On what operating system? +4.20130501-gd9e288b, on ubuntu 13.04 + +### Please provide any additional information below. +Transcript +http://paste.ubuntu.com/5626517/ + +Note: The problem is most likely caused by bad data from either the nntp hooks program, or the nntp server itself. + +I also have one file with bad data that consistently is NOT a problem for gpg to handle(lines 24-25 of log).