aboutsummaryrefslogtreecommitdiffstats
path: root/recipes/opensync/msynctool_0.22.bb
diff options
context:
space:
mode:
authorKlaus Schwarzkopf <schwarzkopf@sensortherm.de>2010-12-05 13:18:47 +0100
committerEric Bénard <eric@eukrea.com>2010-12-09 21:53:10 +0100
commit157adffd31ea5cb79bdf823402c87cea94bf0501 (patch)
tree1b9b9a79f6a58ef802fbeffda1b8def18c4a98ba /recipes/opensync/msynctool_0.22.bb
parent8c56bc9a03bea6877eb81b9584fbf9ed9b45910f (diff)
downloadopenembedded-157adffd31ea5cb79bdf823402c87cea94bf0501.tar.gz
asterisk_1.2.24: Set correct Checksum
Tilghman Lesher <tlesher@digium.com> wrote on asterisk-users@lists.digium.com: Due to a licensing issue with some of the files we distributed with previous tarballs, we removed those files from archived tarballs in order to avoid continuing to distribute those files in any form. So yes, the checksums will have changed, although the checksums we distribute with the tarballs were also updated at the same time. Given that most of the changes since 1.2.24 have been security fixes, I would strongly encourage you to update your packages. There is no excuse for distributing vulnerable packages beyond the date that the vulnerability is disclosed, plus a brief period necessary for releasing updated packages. Additionally, the 1.2 branch has been EOLed, which means if any additional security issues are found, we will not be releasing updated packages to deal with those issues. For this reason, you would be better off putting forth the work to release packages based upon 1.4 or 1.8. Signed-off-by: Klaus Schwarzkopf <schwarzkopf@sensortherm.de> Signed-off-by: Eric Bénard <eric@eukrea.com>
Diffstat (limited to 'recipes/opensync/msynctool_0.22.bb')
0 files changed, 0 insertions, 0 deletions