The Holy Hand Grenade of Antioch - OpenSSL Blog
The OpenSSL Management Committee has been looking at the versioning scheme that is currently in use. Over the years we’ve received plenty of feedback about the “uniqueness” of this scheme, and it does cause some confusion for some users. We would like to adopt a more typical version numbering approach. The current versioning scheme has this format: MAJOR.MINOR.FIX[PATCH] The new scheme will have t
OpenSSL 3.0 Has Been Released! - OpenSSL Blog
After 3 years of development work, 17 alpha releases, 2 beta releases, over 7,500 commits and contributions from over 350 different authors we have finally released OpenSSL 3.0! In addition to this there has been a large number of contributions from our users who have been actively working with the pre-release versions to test it, make sure it works in the real world and with a large array of diff
[ Changelog ] - /news/changelog.html
Changelog When a release is created, that branch is forked off, and its changelog is also forked. For example, none of the changes after 0.9.8n appear in the other logs, because 1.0.0 was created after that release and before 0.9.8o. Any changes that are merged across branches, however, should have an entry in each branch’s changelog. This is the changelog for the master branch, the one that is cu
/policies/releasestrat.html
Release Strategy First issued 23rd December 2014 Last modified 30th November 2023 From 3.0.0 and above, the OpenSSL versioning scheme uses the format: MAJOR.MINOR.PATCH With this format, API/ABI compatibility will be guaranteed for the same MAJOR version number. MAJOR: API/ABI incompatible changes will increase this number MINOR: API/ABI compatible feature releases will change this PATCH: Bug fix
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
OpenSSL Security Advisory [3 Dec 2015]
OpenSSL Security Advisory [19 Mar 2015]
[PDF] This POODLE Bites: Exploiting The SSL 3.0 Fallback
