New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #7862] Segfault in CA handling #2340
Comments
Updated by mfrosch on 2014-11-26 20:44:45 +00:00 Here is a full backtrace with all debuginfo.
pkey=0x649910, type=0x0) at a_sign.c:232
No locals.
serialfile=...) at /usr/src/debug/icinga2-2.2.0/lib/base/tlsutility.cpp:415 PRETTY_FUNCTION = "boost::shared_ptr<x509_st> icinga::CreateCert(EVP_PKEY**, X509_NAME**, X509_NAME**, EVP_PKEY**, bool, const icinga::String&)"
at /usr/src/debug/icinga2-2.2.0/lib/base/tlsutility.cpp:293 PRETTY_FUNCTION = "int icinga::MakeX509CSR(const icinga::String&, const icinga::String&, const icinga::String&, const icinga::String&, bool)"
cadir = {static NPos = 18446744073709551615, m_Data = {static npos = 18446744073709551615, M_dataplus = {<std::allocator> = {<_gnu_cxx::new_allocator> = {}, }, M_dataplus = {<std::allocator> = {<_gnu_cxx::new_allocator> = {}, },
args = {<std::_Vector_base<std::basic_string<char, std::char_traits, std::allocator >, std::allocator<std::basic_string<char, std::char_traits, std::allocator > > >> = { M_impl = {<std::allocator<std::basic_string<char, std::char_traits, std::allocator > >> = {<_gnu_cxx::new_allocator<std::basic_string<char, std::char_traits, std::allocator > >> = {}, }, M_dataplus = {<std::allocator> = {<_gnu_cxx::new_allocator> = {}, }, M_impl = {<std::allocator<boost::shared_ptrboost::program_options::option_description >> = {<_gnu_cxx::new_allocator<boost::shared_ptrboost::program_options::option_description >> = {}, }, _M_start = 0x6303e0, M_impl = {<std::allocator> = {<_gnu_cxx::new_allocator> = {}, }, M_impl = {<std::allocator<boost::shared_ptrboost::program_options::options_description >> = {<_gnu_cxx::new_allocator<boost::shared_ptrboost::program_options::options_description >> = {}, }, _M_start = 0x630a70, M_dataplus = {<std::allocator> = {<_gnu_cxx::new_allocator> = {}, }, M_impl = {<std::allocator<boost::shared_ptrboost::program_options::option_description >> = {<_gnu_cxx::new_allocator<boost::shared_ptrboost::program_options::option_description >> = {}, }, _M_start = 0x630900, M_impl = {<std::allocator> = {<_gnu_cxx::new_allocator> = {}, }, M_impl = {<std::allocator<boost::shared_ptrboost::program_options::options_description >> = {<_gnu_cxx::new_allocator<boost::shared_ptrboost::program_options::options_description >> = {}, }, _M_start = 0x0, M_impl = {<std::allocator<std::basic_string<char, std::char_traits, std::allocator > >> = {<_gnu_cxx::new_allocator<std::basic_string<char, std::char_traits, std::allocator > >> = {}, }, M_dataplus = {<std::allocator> = {<_gnu_cxx::new_allocator> = {}, }, M_dataplus = {<std::allocator> = {<_gnu_cxx::new_allocator> = {}, }, M_dataplus = {<std::allocator> = {<_gnu_cxx::new_allocator> = {}, },
rc = |
Updated by gbeutner on 2014-11-27 08:34:09 +00:00
Apparently OpenSSL < 1.0.0 doesn't allow passing NULL as the MD type for X509_sign(). |
Updated by gbeutner on 2014-11-27 08:40:03 +00:00
Applied in changeset a8b7710. |
Updated by mfriedrich on 2015-03-23 15:10:55 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/7862
Created by mfrosch on 2014-11-26 19:41:32 +00:00
Assignee: gbeutner
Status: Resolved (closed on 2014-11-27 08:40:03 +00:00)
Target Version: 2.2.1
Last Update: 2014-11-27 08:40:03 +00:00 (in Redmine)
I noticed a segmentation fault in the CA handling, at least in "new-ca".
The key was created, but it seems the certificate self-signing fails.
OS: SLES 11 SP3
Package Sources: https://build.opensuse.org/package/show/home:lazyfrosch:icinga2/icinga2
Tell me if you need further details.
pkey=0x649910, type=0x0) at a_sign.c:232
() from /usr/lib64/icinga2/libbase.so
Changesets
2014-11-27 08:35:24 +00:00 by gbeutner a8b7710
2014-11-27 08:54:44 +00:00 by gbeutner bd2861b
Relations:
The text was updated successfully, but these errors were encountered: