You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/12/09 17:10:00 UTC
[jira] [Commented] (OPENMEETINGS-1782) Download page should use
HTTPS/SSL for sigs and hashes
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284836#comment-16284836 ]
ASF subversion and git services commented on OPENMEETINGS-1782:
---------------------------------------------------------------
Commit bf9832a1ee1307356fbfbc36be1b05340634265d in openmeetings's branch refs/heads/4.0.x from [~solomax]
[ https://git-wip-us.apache.org/repos/asf?p=openmeetings.git;h=bf9832a ]
[OPENMEETINGS-1782] https is used instead of http, link to the instructions for verify are added
> Download page should use HTTPS/SSL for sigs and hashes
> ------------------------------------------------------
>
> Key: OPENMEETINGS-1782
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1782
> Project: Openmeetings
> Issue Type: Task
> Reporter: Sebb
> Assignee: Maxim Solodovnik
>
> As the subject says, please use HTTPS rather than HTTP for links to sigs and hashes (as has been done for the KEYS file).
> The page says:
> "All downloads can be verified"
> This is not really strong enough; it should read:
> "All downloads should be verified"
> It would also be useful to link to a page describing how to verify downloads.
> For example: https://www.apache.org/dyn/closer.cgi#verify
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)