[jira] [Commented] (QPID-1834) Misconfiguration of config path for Debian libsasl2-2 (SASL support)
[ https://issues.apache.org/jira/browse/QPID-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13069136#comment-13069136 ] Sam Hendley commented on QPID-1834: --- I just tried this on ubunutu and it doesn't seem to have any affect. I see the log message in the qpidd logs: info SASL: config path set to /etc/sasl2/qpidd.conf But when I try connecting it is still looking at /etc/sasldb2. I verified this by adding different users to /etc/sasldb2 and /var/lib/qpidd/qpidd.sasldb and attempting to log in with both, the ones listed in /etc/sasldb2 worked. I built qpidd using the PPA package on launchpad. This is not a blocker for me, I can just use default sasldb2 location, but the sasl-config option doesn't appear to do the job fully. Misconfiguration of config path for Debian libsasl2-2 (SASL support) Key: QPID-1834 URL: https://issues.apache.org/jira/browse/QPID-1834 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: M4 Environment: Debian squeeze Reporter: Garrett Smith The libsasl2-2 package is configured with the option: --with-configdir=/etc/sasl:/usr/lib/sasl2 Background on this decision can be found here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=211156 cpp/etc/Makefile.in specifies SASL_CONF as /etc/sasl2, which isn't on the config path that the Debian package is compiled with. The result is that the qpid sasl configuration is never used. This is a pain to debug as the missed configuration is silently ignored. I'm not sure what the ideal solution is here, but I think this ought to be addressed given we're talking about Debian. A config option for qpidd would probably be appropriate, or, in keeping with the hard coding strategy, create a link from /etc/sasl to /etc/sasl2. Just a couple ideas though. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2354) ruby client exchange declaration doesn't allow 'type' argument
[ https://issues.apache.org/jira/browse/QPID-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847072#action_12847072 ] Sam Hendley commented on QPID-2354: --- This issue appears to have been fixed in revision 787663 or git commit 3b6e761395b5ce3ad22b20dc1a917e47ea1447e9. ruby client exchange declaration doesn't allow 'type' argument -- Key: QPID-2354 URL: https://issues.apache.org/jira/browse/QPID-2354 Project: Qpid Issue Type: Bug Components: Ruby Client Affects Versions: 0.5 Environment: Ubuntu/Qpid-0.5 Reporter: Andrea Barisani Due to the way function arguments are treated/overrided in the driver it is currently impossible to issue the following command: session.exchange_declare(name, :type = 'fanout') as the :type variable is shadowed within qpid/datatypes.rb struct method. A quick workaround is changing the xml spec with a different name (very nasty though) and everything works (confirming that the attribute is actually honoured). Cheers -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2405) SASL-Ruby binding can cause seg_faults
[ https://issues.apache.org/jira/browse/QPID-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847077#action_12847077 ] Sam Hendley commented on QPID-2405: --- I updated this patch against the trunk 0.6 codebase, my earlier patch had a bug that allowed a different sort of segfault in rare cases. http://github.com/samhendley/qpid/commit/09b0a17b08c8fd0f01be701c8342297b8aab6c1b SASL-Ruby binding can cause seg_faults Key: QPID-2405 URL: https://issues.apache.org/jira/browse/QPID-2405 Project: Qpid Issue Type: Bug Components: Ruby Client Affects Versions: 0.5 Environment: Ubuntu, ruby 1.8.7, qpid 0.5 Reporter: Sam Hendley Assignee: Ted Ross Fix For: 0.5 Attachments: sasl.patch There is an issue with the sasl bindings where it returns a raw ruby VALUE type for the sasl context. This works _UNTIL_ the ruby runtime tries to access that variable which then causes a segfault. This is easy to see if you try to inspect the variable at all (like print it or ask for its class or methods). In my application, for reasons I haven't determined yet, just having this variable on the heap meant that when an exception occurred trying to print the exceptions message caused a seg fault. In any case, passing back raw VALUEs to ruby code is a Bad Idea and goes against the spec. There is a simple macro and fix for this which wraps the returned value in a ruby object. This fixes the issue I was having and means the deleting of the object is done automatically (instead of having a manual free function). I have a patch with the simple, low impact fix, really it would be better to the extension so the sasl client is repersented as a real ruby object but that would require atleast some client code changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2405) SASL-Ruby binding can cause seg_faults
SASL-Ruby binding can cause seg_faults Key: QPID-2405 URL: https://issues.apache.org/jira/browse/QPID-2405 Project: Qpid Issue Type: Bug Components: Ruby Client Affects Versions: 0.5 Environment: Ubuntu, ruby 1.8.7, qpid 0.5 Reporter: Sam Hendley Fix For: 0.5 There is an issue with the sasl bindings where it returns a raw ruby VALUE type for the sasl context. This works _UNTIL_ the ruby runtime tries to access that variable which then causes a segfault. This is easy to see if you try to inspect the variable at all (like print it or ask for its class or methods). In my application, for reasons I haven't determined yet, just having this variable on the heap meant that when an exception occurred trying to print the exceptions message caused a seg fault. In any case, passing back raw VALUEs to ruby code is a Bad Idea and goes against the spec. There is a simple macro and fix for this which wraps the returned value in a ruby object. This fixes the issue I was having and means the deleting of the object is done automatically (instead of having a manual free function). I have a patch with the simple, low impact fix, really it would be better to the extension so the sasl client is repersented as a real ruby object but that would require atleast some client code changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2405) SASL-Ruby binding can cause seg_faults
[ https://issues.apache.org/jira/browse/QPID-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Hendley updated QPID-2405: -- Attachment: sasl.patch Low impact fix to prevent seg faults by wrapping the raw value in a ruby object. SASL-Ruby binding can cause seg_faults Key: QPID-2405 URL: https://issues.apache.org/jira/browse/QPID-2405 Project: Qpid Issue Type: Bug Components: Ruby Client Affects Versions: 0.5 Environment: Ubuntu, ruby 1.8.7, qpid 0.5 Reporter: Sam Hendley Fix For: 0.5 Attachments: sasl.patch There is an issue with the sasl bindings where it returns a raw ruby VALUE type for the sasl context. This works _UNTIL_ the ruby runtime tries to access that variable which then causes a segfault. This is easy to see if you try to inspect the variable at all (like print it or ask for its class or methods). In my application, for reasons I haven't determined yet, just having this variable on the heap meant that when an exception occurred trying to print the exceptions message caused a seg fault. In any case, passing back raw VALUEs to ruby code is a Bad Idea and goes against the spec. There is a simple macro and fix for this which wraps the returned value in a ruby object. This fixes the issue I was having and means the deleting of the object is done automatically (instead of having a manual free function). I have a patch with the simple, low impact fix, really it would be better to the extension so the sasl client is repersented as a real ruby object but that would require atleast some client code changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1811) Unable to compile qpid on FreeBSD
[ https://issues.apache.org/jira/browse/QPID-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802353#action_12802353 ] Sam Hendley commented on QPID-1811: --- I agree with you, we have been looking at this issue as well, trying to compile for cygwin and arm. I have been thinking of using boost threading and boost asio to make new target that matches the implict interface of the posix/solaris and windows system implementations. This is a pattern we have used for some of our own projects, we started writing platform specific code for the system specific stuff like threading and locks and then found we could replace it all with boost constructs. One nice thing about going that route is we were forced to treat the system specific stuff like a black box from the main code (as qpid has done) so it made the transition to boos/asio very easy. QPid may be similar, they allready are carrying all of the necessary boost dependecies for asio so thats a big plus. Unable to compile qpid on FreeBSD - Key: QPID-1811 URL: https://issues.apache.org/jira/browse/QPID-1811 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: FreeBSD 8-CURRENT on amd64 (64 bit) $ g++ -v Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] $ python -V Python 2.6.1 $ pkg_info | grep boost boost-python-1.37.0 Free peer-reviewed portable C++ source libraries svn trunk version, checked out now (r765092) ./configure CPPFLAGS=-I/usr/local/include -L/usr/local/lib LDFLAGS=-L/usr/local/lib --with-poller=poll Reporter: Attila Nagy Priority: Blocker Attachments: qpidfbsdcompile.diff I'm trying to build qpid c++ broker on FreeBSD. Problems found during the build process: -8- g++ -DHAVE_CONFIG_H -I. -Igen -I./gen -I/usr/local/include -Werror -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers -Woverloaded-virtual -g -O2 -MT qpid/sys/posix/Thread.lo -MD -MP -MF qpid/sys/posix/.deps/Thread.Tpo -c qpid/sys/posix/Thread.cpp -fPIC -DPIC -o qpid/sys/posix/.libs/Thread.o qpid/sys/posix/Thread.cpp: In member function 'long unsigned int qpid::sys::Thread::id()': qpid/sys/posix/Thread.cpp:64: error: invalid conversion from 'pthread*' to 'long unsigned int' I don't know whether it helps during the run, but allows to compile: return (unsigned long)impl-thread; -8- g++ -DHAVE_CONFIG_H -I. -Igen -I./gen -I/usr/local/include -Werror -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers -Woverloaded-virtual -g -O2 -MT qpid/sys/posix/SystemInfo.lo -MD -MP -MF qpid/sys/posix/.deps/SystemInfo.Tpo -c qpid/sys/posix/SystemInfo.cpp -fPIC -DPIC -o qpid/sys/posix/.libs/SystemInfo.o In file included from qpid/sys/posix/SystemInfo.cpp:25: /usr/include/net/if.h:293: error: field 'ifru_addr' has incomplete type /usr/include/net/if.h:294: error: field 'ifru_dstaddr' has incomplete type /usr/include/net/if.h:295: error: field 'ifru_broadaddr' has incomplete type /usr/include/net/if.h:327: error: field 'ifra_addr' has incomplete type /usr/include/net/if.h:328: error: field 'ifra_broadaddr' has incomplete type /usr/include/net/if.h:329: error: field 'ifra_mask' has incomplete type /usr/include/net/if.h:427: error: field 'addr' has incomplete type /usr/include/net/if.h:428: error: field 'dstaddr' has incomplete type qpid/sys/posix/SystemInfo.cpp: In function 'void qpid::sys::SystemInfo::getLocalIpAddresses(uint16_t, std::vectorqpid::Address, std::allocatorqpid::Address )': qpid/sys/posix/SystemInfo.cpp:63: error: 'PF_INET' was not declared in this scope qpid/sys/posix/SystemInfo.cpp:63: error: 'SOCK_STREAM' was not declared in this scope qpid/sys/posix/SystemInfo.cpp:63: error: 'socket' was not declared in this scope qpid/sys/posix/SystemInfo.cpp:66: error: 'struct ifreq' has no member named 'ifr_ifindex' qpid/sys/posix/SystemInfo.cpp:67: error: 'SIOCGIFNAME' was not declared in this scope qpid/sys/posix/SystemInfo.cpp:72: error: 'union ifreq::anonymous' has no member named 'ifru_addr' qpid/sys/posix/SystemInfo.cpp:73: error: invalid use of incomplete type 'struct qpid::sys::sockaddr_in' qpid/sys/posix/SystemInfo.cpp:72: error: forward declaration of 'struct
[jira] Commented: (QPID-2264) The Build Instructions for the Ruby bits could use some love
[
https://issues.apache.org/jira/browse/QPID-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799231#action_12799231
]
Sam Hendley commented on QPID-2264:
---
You should really just fix the gem specification so it adds the sasl components
and qpid code so it builds sasl correctly. This makes it the easiest to use. It
only takes one line to fix this in the Rakefile(line 108):
s.extensions 'ext/sasl/extconf.rb'
I had more comments here:
http://mercenary-code.blogspot.com/2010/01/qpid-ruby-driver.html
The Build Instructions for the Ruby bits could use some love
Key: QPID-2264
URL: https://issues.apache.org/jira/browse/QPID-2264
Project: Qpid
Issue Type: Improvement
Components: Ruby Client
Reporter: Bryan Kearney
In order to build the ruby bits, I needed to install the following:
rake, ruby-devel, cyrus-sasl-devel
To run against this, I needed to do a
rake build
and then I had to:
export RUBYLIB={QPIDHOME}qpid/qpid/ruby/lib:{QPIDHOME}qpid/qpid/ruby/ext/sasl
It would be nice for this to be in the doco.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
