{"action":"created","issue":{"url":"https://api.github.com/repos/JabRef/jabref/issues/942","repository_url":"https://api.github.com/repos/JabRef/jabref","labels_url":"https://api.github.com/repos/JabRef/jabref/issues/942/labels{/name}","comments_url":"https://api.github.com/repos/JabRef/jabref/issues/942/comments","events_url":"https://api.github.com/repos/JabRef/jabref/issues/942/events","html_url":"https://github.com/JabRef/jabref/pull/942","id":140253238,"number":942,"title":"Add support for write-protected PDFs","user":{"login":"koppor","id":1366654,"avatar_url":"https://avatars.githubusercontent.com/u/1366654?v=3","gravatar_id":"","url":"https://api.github.com/users/koppor","html_url":"https://github.com/koppor","followers_url":"https://api.github.com/users/koppor/followers","following_url":"https://api.github.com/users/koppor/following{/other_user}","gists_url":"https://api.github.com/users/koppor/gists{/gist_id}","starred_url":"https://api.github.com/users/koppor/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/koppor/subscriptions","organizations_url":"https://api.github.com/users/koppor/orgs","repos_url":"https://api.github.com/users/koppor/repos","events_url":"https://api.github.com/users/koppor/events{/privacy}","received_events_url":"https://api.github.com/users/koppor/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-11T18:11:00Z","updated_at":"2016-03-11T22:11:58Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/JabRef/jabref/pulls/942","html_url":"https://github.com/JabRef/jabref/pull/942","diff_url":"https://github.com/JabRef/jabref/pull/942.diff","patch_url":"https://github.com/JabRef/jabref/pull/942.patch"},"body":"This fixes #935.\r\n\r\nWhen importing PDFs, which carry a password for editing, both the XMP Metadata parser and the PDFContentImporter can handle this.\r\n\r\nNow, the [Legion of the Bouncy Castle Java cryptography APIs](http://bouncycastle.org/java.html) are part of JabRef, which makes JabRef subject to export restrictions. [Bouncy Castle is approved classified under ECCN code 5D002 and approved for export under License Exception TSU](http://www.bouncycastle.org/wiki/display/JA1/Frequently+Asked+Questions#FrequentlyAskedQuestions-11.WhatisBouncyCastle%27sexportclassificationintheUnitedStatesofAmerica?). According to https://www.bis.doc.gov/index.php/policy-guidance/encryption/classification, JabRef can now only be exported \"to any end-user located or headquartered in a country listed in Supplement No. 3 to Part 740\", which is [AustriaAustraliaBelgiumBulgariaCanadaCyprusCzech RepublicEstoniaDenmarkFinlandFranceGermanyGreeceHungaryIcelandIrelandItalyJapanLatviaLithuaniaLuxembourgMaltaNetherlandsNew ZealandNorwayPolandPortugalRomaniaSlovakiaSloveniaSpainSwedenSwitzerlandTurkeyUnited Kingdom](https://www.law.cornell.edu/cfr/text/15/part-740/appendix-SupplementNo3).\r\n\r\nThe current code, however, also allows BouncyCastle to be removed and JabRef still compiles. It internally throw a NoClassDefFound Exception, which is handled properly.\r\n\r\nI am unsure, how to proceed. [Debian also distributes bouncy-castle](https://packages.debian.org/de/sid/libbcprov-java)."},"comment":{"url":"https://api.github.com/repos/JabRef/jabref/issues/comments/195573015","html_url":"https://github.com/JabRef/jabref/pull/942#issuecomment-195573015","issue_url":"https://api.github.com/repos/JabRef/jabref/issues/942","id":195573015,"user":{"login":"Siedlerchr","id":320228,"avatar_url":"https://avatars.githubusercontent.com/u/320228?v=3","gravatar_id":"","url":"https://api.github.com/users/Siedlerchr","html_url":"https://github.com/Siedlerchr","followers_url":"https://api.github.com/users/Siedlerchr/followers","following_url":"https://api.github.com/users/Siedlerchr/following{/other_user}","gists_url":"https://api.github.com/users/Siedlerchr/gists{/gist_id}","starred_url":"https://api.github.com/users/Siedlerchr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Siedlerchr/subscriptions","organizations_url":"https://api.github.com/users/Siedlerchr/orgs","repos_url":"https://api.github.com/users/Siedlerchr/repos","events_url":"https://api.github.com/users/Siedlerchr/events{/privacy}","received_events_url":"https://api.github.com/users/Siedlerchr/received_events","type":"User","site_admin":false},"created_at":"2016-03-11T22:11:58Z","updated_at":"2016-03-11T22:11:58Z","body":"From what I understand in this discussion, that the US exporting laws would apply if you distribute the software from an US Server:\r\nhttp://security.stackexchange.com/questions/7015/us-export-control-on-open-source-libraries\r\n\r\nThe best solution would be to load it dynamically and not distribute it with JabRef.\r\nThen users can download the library, put them in the folder and use it.\r\n\r\n"}}