Comments (30)
I send transfer offer to openssl
owner.
from openssl.
I contacted the current owner at mbailey/openssl#1 and @mbailey agreed with releasing the gem namespace.
from openssl.
oops. Should I continue to transfer negotiation instead of you?
And I sometimes request to remove stdlib protection to rubygems admins. see. rubygems/rubygems.org#1273
from openssl.
commented mbailey/openssl#1 (comment)
from openssl.
note: rubygems/rubygems#1663 , rubygems/rubygems.org#1373
from openssl.
I guess we still need to decide a version number?
from openssl.
@rhenium I've been promoted openssl owner by rubygems admins. Can you give your mail address on rubygems?
from openssl.
@hsbt Thank you always! My email is k(at)rhe.jp.
from openssl.
@rhenium I added owner grant to you. If you are ready to ship openssl gem, I'm going to request to remove openssl from rubygems blacklist.
from openssl.
@hsbt Thanks!
It looks like openssl is already excluded from the list, at least in the source repository. rubygems/rubygems.org@6e74bd9
I think we can release now if only we decide the version number.
from openssl.
@hsbt @rhenium お疲れさまです! I will review #59 and commit my changes to the documentation.
Regarding the NEWS
, as of 1b8bcdb the organization is:
- Compatibility
- Updates since 2.3 (in order of class)
However, there is some duplication between the updates and compatibility list.
I will review this too, but first I think we could split it up similar to Rails release notes as such:
- Compatibility notes (with regards to OpenSSL versions)
- Supported platforms (with current release)
- Changes in current release
Changes would include the following:
- Notable changes (such as breaking api, or additions, features, etc)
- Removals (Already deprecated features that were removed)
- Deprecations (Stuff to be removed next release)
One other idea is after the release is made, we should consider moving the NEWS
document like we do with Ruby, i.e.: docs/NEWS-2.4.0
Thanks for taking the time to work on this and prepare the release!
I will submit my thoughts in the form of a patch :)
from openssl.
@zzak Thanks! That's a great help.
One other idea is after the release is made, we should consider moving the NEWS document like we do with Ruby, i.e.: docs/NEWS-2.4.0
I think we can just append on top, each release note would be smaller than Ruby. Maybe I should have named it History
.
from openssl.
Append is also fine! Let's go with History
.
from openssl.
@rhenium @hsbt I sent a PR with my changes, please check it when you're ready
I think we can also close #54 once this is done, thanks!!
from openssl.
@zzak Thank you! It looks much nicer! Do you have suggestions on changes in README.md and CONTRIBURING.md?
from openssl.
@rhenium Thanks, I will review.
from openssl.
OpenSSL::VERSION
already retunes "1.1.0". We should use 2.0.0 when releasing openssl gem.
from openssl.
OpenSSL 1.1.0 was just released today, and Ruby/OpenSSL looks working fine with it: https://travis-ci.org/ruby/openssl/builds/155282416
Is there still a blocker for the release?
from openssl.
Is there still a blocker for the release?
There is no blocker for me
from openssl.
I have no blockers, version 2.0.0 sounds fine.
Let's yank the current gems from rubygems.org and cut a pre-release?
from openssl.
Let's yank the current gems from rubygems.org and cut a pre-release?
I think so! Can I do that?
from openssl.
@rhenium Yes, if you are authenticated on rubygems.org, via the gem
command you can yank the old versions with:
gem yank openssl -v '0.2.0'
gem yank openssl -v '0.1.0'
And to publish (after updating version.rb
):
gem build openssl.gemspec
gem push openss-2.0.0.beta1.gem
For example if you wanted to choose "beta1" as the first pre-release.
from openssl.
Just pushed openssl-2.0.0.beta1: https://rubygems.org/gems/openssl
from openssl.
Imported to trunk at: ruby/ruby@c9dc016
from openssl.
@rhenium Ah great!
Btw, I think two things are missing in History from #18, that is ALPN and ECDH callback support.
We can add it to the news in the next beta/rc?
edit: also, I want to "linkify" the History.md
so we can click through the tickets/PRs from there
from openssl.
Linkify in #69
from openssl.
@tenderlove BTW bro, the tmp_ecdh_callback
stuff was removed in favor of ecdh_curves
: https://github.com/ruby/openssl/blob/v2.0.0.beta.1/History.md#deprecations
from openssl.
@zzak ALPN and ECDH callback are part of Ruby 2.3 (though they aren't in doc/NEWS-2.3.0).
from openssl.
@rhenium Ahh, ok! I will revert 59b22d4 then.
from openssl.
Gem ship is done. ref. https://rubygems.org/gems/openssl/versions/2.0.0.beta.1
from openssl.
Related Issues (20)
- Support OpenSSL 3 FIPS HOT 33
- OpenSSL 3: OpenSSL.fips_mode returns false in FIPS enabled environment HOT 5
- Test failure with OpenSSL 3.1.0 HOT 3
- Missing `shutdown`, `close_write` and `close_read`. HOT 1
- Non-blocking socket not handled correctly. HOT 4
- OpenSSL::PKCS12 error: PKCS12_parse: unsupported HOT 4
- undefined method 'to_octet_string' for OpenSSL::PKey::EC HOT 1
- GCC -L<openssl lib directory> is wrong with the OpenSSL installed from the souce without --libdir=lib option HOT 2
- pkeys are immutable on OpenSSL 3.0\e[0m (OpenSSL::PKey::PKeyError) HOT 1
- Warning: "OPENSSL_FIPS" is not defined, evaluates to 0 [-Wundef] HOT 1
- Checking compiler warnings as errors on CI HOT 6
- lib/openssl/hmac.rb:55:in `initialize': EVP_PKEY_new_mac_key: malloc failure (OpenSSL::HMACError) with -Werror flag HOT 12
- Group Key Agreement using OpenSSL HOT 1
- `EVP_DigestSignInit: unsupported (OpenSSL::HMACError)` and `Digest initialization failed: initialization error (OpenSSL::Digest::DigestError)` HOT 4
- OpenSSL 3 FIPS mode - creating encrypted RSA key pair fails with PEM_write_bio_PrivateKey_traditional: initialization error (OpenSSL::PKey::PKeyError) HOT 7
- openssl 3.1.0 security issues HOT 2
- Can no longer pass file contents as ca_file property with OpenSSL 3 HOT 3
- warning: macOS truffleruby-head: TS_VERIFY_CTS_set_certs macro redefined in OpenSSL 3.1 HOT 25
- New OpenSSL gem release HOT 4
- Issue imporitng certificates created using OpenSSL::PKCS12 on macOS devices HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openssl.