Issue 228 in freemedforms: Datapacks should be GPG-signed

0 views
Skip to first unread message

freeme...@googlecode.com

unread,
Nov 28, 2012, 4:50:57 PM11/28/12
to freemedf...@googlegroups.com
Status: Accepted
Owner: christian.a.reiter
Labels: Type-Enhancement Priority-High Milestone-Release1.0

New issue 228 by christian.a.reiter: Datapacks should be GPG-signed
http://code.google.com/p/freemedforms/issues/detail?id=228

In a medical application there must be secured that all downloaded
datapacks are truly from the source that they claim they are.

This could be easily done by signing them with a private/public async GPG
signing system.
While downloading a datapack the GPG signature can be verified and if it
isn't correct, FMF refuses to install the datapack.

freeme...@googlecode.com

unread,
Sep 15, 2013, 1:09:14 PM9/15/13
to freemedf...@googlegroups.com
Updates:
Labels: -Milestone-Release1.0 Milestone-Release2.0

Comment #1 on issue 228 by eric.mae...@gmail.com: Datapacks should be
GPG-signed
http://code.google.com/p/freemedforms/issues/detail?id=228

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

freeme...@googlecode.com

unread,
Aug 2, 2014, 7:14:58 AM8/2/14
to freemedf...@googlegroups.com
Updates:
Owner: con...@medecinelibre.com
Cc: eric.mae...@gmail.com

Comment #2 on issue 228 by eric.mae...@gmail.com: Datapacks should be
Reply all
Reply to author
Forward
0 new messages