Summary: | The use of ruby-odbc on Gentoo Hardened leads to "INTERN (0) [RubyODBC]Cannot allocate SQLHENV (ODBC::Error)" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Christoph Mueller <chris> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Team <hardened> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | pappy, ruby |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Customized ebuild of ruby-odbc |
Description
Christoph Mueller
2007-05-25 15:43:53 UTC
Created attachment 120296 [details]
Customized ebuild of ruby-odbc
This is a customized ebuild of ruby-odbc that introduces a new use flag "nodlopen" so you can control whether dlopen is used. Default is to use it.
thx Is this still an issue with ruby-odbc-0.99991 ? (In reply to comment #3) > Is this still an issue with ruby-odbc-0.99991 ? Hi Hans, Yes,the same error occures with 0.99991. The only way to get it to work is with my custom ebuild... Greetings,,, I think having a USE flag for that is not a good solution, because it is not intuitive. If the build fails people won't really know to use nodlopen unless they happen to find this bug. Ideally we should have some kind of solution that either selects this option when using a hardened compiler automatically, or simply not use dlopen at all, but I'm not sure what the implication is for normal builds. @hardened: any advice on how to handle this? Force-disable dlopen. This way it's linked at build-time which generally speaking is a better choice, for a distribution like ours, because it disallows users from trying to load libraries with different ABI. (In reply to comment #6) > Force-disable dlopen. This way it's linked at build-time which generally > speaking is a better choice, for a distribution like ours, because it disallows > users from trying to load libraries with different ABI. Fixed in ruby-odbc-0.99991-r1. Thank you! Great! |