diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-05-31 17:25:45 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-05-31 17:25:45 -0400 |
| commit | 2b990dc0149e20a3a0949f898f5950670da57c64 (patch) | |
| tree | 6cc9c9a742e279d4dcd26879b155b7f715c147c7 | |
| parent | 628946c317bd60f2068782eadf5774f987f7a13d (diff) | |
moreinfo
| -rw-r--r-- | doc/bugs/gpg_goes_to_100__37___cpu_on_bad_input_data.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
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 index 10840736f..5f36a7cd0 100644 --- 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 @@ -14,3 +14,5 @@ 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]] |