aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/gpg_goes_to_100__37___cpu_on_bad_input_data.mdwn
blob: 5f36a7cd0d7b9b660ef576718b8faf407ba0fb3d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
### 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 data

### 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).

[[!tag moreinfo]]