-
Notifications
You must be signed in to change notification settings - Fork 81
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
the default cert could be PEM or a java keystore. it should load both…
… whatver is used as default.
- v0.15.3
- v0.15.2
- v0.15.1
- v0.15.0
- v0.14.6
- v0.14.5
- v0.14.4
- v0.14.3
- v0.14.2
- v0.14.1
- v0.14.1.cr2
- v0.14.1.cr1
- v0.14.0
- v0.13.0
- v0.12.2
- v0.12.1
- v0.12.0
- v0.11.0
- v0.10.7
- v0.10.6
- v0.10.5
- v0.10.4
- v0.10.3
- v0.10.2
- v0.10.1
- v0.10.0
- v0.9.21
- v0.9.20
- v0.9.19
- v0.9.18
- v0.9.17
- v0.9.16
- v0.9.15
- v0.9.14
- v0.9.13
- v0.9.12
- v0.9.11
- v0.9.10
Showing
3 changed files
with
24 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
module Jopenssl | ||
module Version | ||
VERSION = '0.9.9' | ||
VERSION = '0.9.10' | ||
BOUNCY_CASTLE_VERSION = '1.50' | ||
end | ||
end |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1d3ba21
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this change has consequences such as no longer breaking the flow on exceptions e.g.
add_file
set_default_paths
will no longer throw aStoreError
... wish it at least had some tests included - since I'm not sure if that behavioral change is desired thus am inclined to revert (and possibly do decision logic on a higher front than the lowest level helper) ... could this be worked on for a while before rushing into a release?1d3ba21
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "fixed" logic obviously has problems. I'm wondering if we should perhaps revert this change and the keystore change until we understand exactly how we should be doing this search.
1d3ba21
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's not part of 0.9.9 thus that should be good - 0.9.10 seems only in staging (not yet released as a gem)
what (other) key-store change you mean, related to default paths from #61 (part of 0.9.9) ?
1d3ba21
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was not able to see any error in
set_default_paths
on MRI !? example please ! I will see for theadd_file
part.but it is OK to revert those patches. yes, I just closed it on sonatype to be able to use it with jruby-1_7 as if it comes from rubygems.org. so 0.9.10 is not released !!! just drop it on sonatype
1d3ba21
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... probably cause there's not enough tests for all these no where ;( - will drop and test another 0.9.10, thx!
pls try to come up with test-cases - also a hint for the debug helpers on
OpenSSL
there's a reason they're not used outside the "frontend" Ruby classes - this way we get stack-traces always come from the direct caller (we're also avoid potential double-logging), the sub-packages usually do not know much about JRuby's classes - Lookout being (already) an "unfortunate" exception to this since it needs to resolve paths the JRuby-way. I think it's ripe for some refactoring - meaningful/useful tests might show us the path to follow ...1d3ba21
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we are calling the wrong methods on the wrong files but the port of that code has c-style returns. I would argue catching the exceptions is still appropriate OR we change these to be exception throwing vs c-returns. So I think the code needs to change but if we keep c-returns then lets also catch exceptions like this patch does.
1d3ba21
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should qualify my comment a bit more. We should not be trying to load a .pem file as a java keystore (wrong methods on wrong files).
1d3ba21
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@enebo yy ... whole thing seems "hacky" - and that is why we probably better have tests before shipping
1d3ba21
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kares yeah that sounds reasonable to me.