Hi all!
looking into sslsniff [0] I noticed loads of failures in boost::asio
headers like
/usr/include/boost/asio/ip/detail/impl/endpoint.ipp:76:11: error:
‘boost::asio::detail::sockaddr_in4_type’ has no member named ‘v4’
/usr/include/boost/asio/ip/detail/impl/endpoint.ipp:82:11: error:
‘boost::asio::detail::sockaddr_in4_type’ has no member named ‘v6’
I wasn't able to fix them right away, there seems to be some
conditionalizing on __FreeBSD__ / __linux__ / ... and probably some
other weird stuff going wrong. Volunteers for loking into that?
Regards
Christoph
[0] sslnsiff itself has netfilter vs pf hardcoded (at the head of the
file) in util/Destination.cpp which should be fixed either in
configure or by checking for __linux__ some time, the other problem
for sslsniff is the boost::asio problem
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
