[jira] [Updated] (PROTON-390) Suppress or Fix the warnings openssl.c produce
[ https://issues.apache.org/jira/browse/PROTON-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-390: - Description: openssl.c produces lots of warnings. /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c: In function ‘_log_ssl_error’: /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:165: warning: ‘ERR_get_error’ is deprecated (declared at /usr/include/openssl/err.h:266) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:167: warning: ‘ERR_error_string_n’ is deprecated (declared at /usr/include/openssl/err.h:280) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:169: warning: ‘ERR_get_error’ is deprecated (declared at /usr/include/openssl/err.h:266) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c: In function ‘ssl_failed’: /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:189: warning: ‘ERR_get_error’ is deprecated (declared at /usr/include/openssl/err.h:266) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:191: warning: ‘ERR_error_string_n’ is deprecated (declared at /usr/include/openssl/err.h:280) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c: In function ‘verify_callback’: /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:257: warning: ‘X509_STORE_CTX_get_error_depth’ is deprecated (declared at /usr/include/openssl/x509_vfy.h:453) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:261: warning: ‘X509_STORE_CTX_get_current_cert’ is deprecated (declared at /usr/include/openssl/x509_vfy.h:454) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:262: warning: ‘X509_STORE_CTX_get_ex_data’ is deprecated (declared at /usr/include/openssl/x509_vfy.h:450) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:262: warning: ‘SSL_get_ex_data_X509_STORE_CTX_idx’ is deprecated (declared at /usr/include/openssl/ssl.h:1601) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:268: warning: ‘SSL_get_ex_data’ is deprecated (declared at /usr/include/openssl/ssl.h:1587) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:285: warning: ‘X509_get_ext_d2i’ is deprecated (declared at /usr/include/openssl/x509.h:1151) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:287: warning: ‘sk_num’ is deprecated (declared at /usr/include/openssl/stack.h:81) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:290: warning: ‘sk_value’ is deprecated (declared at /usr/include/openssl/stack.h:82) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:295: warning: ‘ASN1_STRING_to_UTF8’ is deprecated (declared at /usr/include/openssl/asn1.h:981) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:299: warning: ‘CRYPTO_free’ is deprecated (declared at /usr/include/openssl/crypto.h:480) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:308: warning: ‘X509_get_subject_name’ is deprecated (declared at /usr/include/openssl/x509.h:1013) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:310: warning: ‘X509_NAME_get_index_by_NID’ is deprecated (declared at /usr/include/openssl/x509.h:1105) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:311: warning: ‘X509_NAME_get_entry’ is deprecated (declared at /usr/include/openssl/x509.h:1108) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:312: warning: ‘X509_NAME_ENTRY_get_data’ is deprecated (declared at /usr/include/openssl/x509.h:1130) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:315: warning: ‘ASN1_STRING_to_UTF8’ is deprecated (declared at /usr/include/openssl/asn1.h:981) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:319: warning: ‘CRYPTO_free’ is deprecated (declared at /usr/include/openssl/crypto.h:480) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:329: warning: ‘X509_STORE_CTX_set_error’ is deprecated (declared at /usr/include/openssl/x509_vfy.h:452) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c: In function ‘get_dh2048’: /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:371: warning: ‘DH_new’ is deprecated (declared at /usr/include/openssl/dh.h:184) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:372: warning: ‘BN_bin2bn’ is deprecated (declared at /usr/include/openssl/bn.h:422) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:373: warning: ‘BN_bin2bn’ is deprecated (declared at /usr/include/openssl/bn.h:422) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:375: warning: ‘DH_free’ is deprecated (declared at /usr/include/openssl/dh.h:185) /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c: In function ‘ssn_cache_find’: /Users/chirino/sandbox/qpid-proton/proton-c/src/ssl/openssl.c:385: warning: ‘SSL_SESSION_get_time’ is deprecated (declared at /usr/include/openssl/ssl.h:1421)
[jira] [Commented] (PROTON-396) Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies.
[ https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733564#comment-13733564 ] Hiram Chirino commented on PROTON-396: -- If you want to keep pn_ssl_t opaque, then I think that the signature on pn_ssl_init needs to change to pass the hostname that's being connected to. pn_ssl_init can then set the ssl-peer_hostname field. Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies. --- Key: PROTON-396 URL: https://issues.apache.org/jira/browse/PROTON-396 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Hiram Chirino -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-396) Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies.
[ https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-396: - Attachment: PROTON-396.patch Attaching a patch that fixes this issue. Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies. --- Key: PROTON-396 URL: https://issues.apache.org/jira/browse/PROTON-396 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Hiram Chirino Attachments: PROTON-396.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: proton-j API factory simplification.
Correct: 'I don't think ProtonJ and ProtonC should reside in the proton-api.jar' On Fri, Aug 2, 2013 at 8:35 AM, Rajith Attapattu rajit...@gmail.com wrote: So, I'd be in favour of Hiram's proposal if ProtonJ and ProtonC reside in proton-api.jar. This would be very easy to do, e.g. I don't think ProtonJ and ProtonC should reside in the proton-api.jar And I don't think thats what Hiram suggested either (pls correct me if I have misunderstood). Only the Proton interface and supported interfaces needs to be there in proton-api.jar. ProtonJ, ProtonC, or any other implementation will be in the respective implementation jars. Apart from testing, I doubt most people will want to switch between implementations the way we have them now. For most it would be an informed decision of choosing a particular implementation after weighing the pros and cons of it. Rajith -- Hiram Chirino Engineering | Red Hat, Inc. hchir...@redhat.com | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino blog: Hiram Chirino's Bit Mojo
[jira] [Commented] (PROTON-396) Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies.
[ https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733772#comment-13733772 ] Hiram Chirino commented on PROTON-396: -- calling pn_ssl_set_peer_hostname after init seem to work fine. :) Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies. --- Key: PROTON-396 URL: https://issues.apache.org/jira/browse/PROTON-396 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Hiram Chirino Attachments: PROTON-396-v2.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PROTON-396) Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies.
[ https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-396: - Attachment: PROTON-396-v2.patch Attaching simpler fix. Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies. --- Key: PROTON-396 URL: https://issues.apache.org/jira/browse/PROTON-396 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Hiram Chirino Attachments: PROTON-396-v2.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (PROTON-396) Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies.
[ https://issues.apache.org/jira/browse/PROTON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-396: - Assignee: Ken Giusti Proton Messenger should configure the SNI headers on it's TLS connections so that those connections can be routed by SNI aware proxies. --- Key: PROTON-396 URL: https://issues.apache.org/jira/browse/PROTON-396 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Hiram Chirino Assignee: Ken Giusti Attachments: PROTON-396-v2.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (PROTON-397) Need an example using the proton-j Messenger and Message API
Marc Berkowitz created PROTON-397: - Summary: Need an example using the proton-j Messenger and Message API Key: PROTON-397 URL: https://issues.apache.org/jira/browse/PROTON-397 Project: Qpid Proton Issue Type: Wish Components: proton-j Affects Versions: 0.4, 0.5 Reporter: Marc Berkowitz Need a java counterpart to proton/examples/messenger/py, with a pair of simple java commaind-line programs that send and receive messages. Fixed bug PROTON-257 does not show how to use interface Messenger. I have a simple version, closely based on examples/messenger/py, which I can contribute, -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (PROTON-398) pn_messenger_subscribe() fails to create a listener
Marc Berkowitz created PROTON-398: - Summary: pn_messenger_subscribe() fails to create a listener Key: PROTON-398 URL: https://issues.apache.org/jira/browse/PROTON-398 Project: Qpid Proton Issue Type: Bug Components: proton-c, proton-j Affects Versions: 0.5 Environment: linux (fedora 14 64bit) Reporter: Marc Berkowitz Running a local ActiveMQ server, release 5.8.0, default configuration. The documented listen all' feature of the python example fails with the error 'bind: Address already in use.' cd proton/examples/messenger/py; ./recv.py amqp://localhost/test -- subscribes to a specified address, and works ./recv.py OR ./recv.py amqp://~localhost -- listens to all addresses, and fails. py/recv.py amqp://~localhost Traceback (most recent call last): File py/recv.py, line 41, in module mng.subscribe(a) File /usr/lib64/python2.7/site-packages/proton.py, line 371, in subscribe self._check(PN_ERR) File /usr/lib64/python2.7/site-packages/proton.py, line 228, in _check raise exc([%s]: %s % (err, pn_messenger_error(self._mng))) proton.MessengerException: [-2]: unable to subscribe to source: amqp://~localhost (bind: Address already in use) Same error from a similar java program, which calls proton-j. Both fail trying to bind to localhost:5672, which is held by the local activemq server. Must either fix the ~ADDRESS feature or remove it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
