monero-project/monero
monero-project/monero
1
0
Fork 0
mirror of https://github.com/monero-project/monero.git synced 2024-11-17 08:17:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Do not require client certificate unless server has some whitelisted.

Browse source 
Currently a client must provide a certificate, even if the server is
configured to allow all certificates. This drops that requirement from
the client - unless the server is configured to use a CA file or
fingerprint(s) for verification - which is the standard behavior for SSL
servers.

The "system-wide" CA is not being used as a "fallback" to verify clients
before or after this patch.
This commit is contained in:
Lee Clagett 2019-03-12 18:16:47 -04:00
parent a3b0284837
commit f18a069fcc
1 changed files with 27 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

39
contrib/epee/src/net_ssl.cpp
View file

@ -302,18 +302,33 @@ bool ssl_handshake(boost::asio::ssl::stream<boost::asio::ip::tcp::socket> &socke
bool verified = false; bool verified = false;
socket.next_layer().set_option(boost::asio::ip::tcp::no_delay(true)); socket.next_layer().set_option(boost::asio::ip::tcp::no_delay(true));
socket.set_verify_mode(boost::asio::ssl::verify_peer); /* Using system-wide CA store for client verification is funky - there is
socket.set_verify_callback([&](bool preverified, boost::asio::ssl::verify_context &ctx) no expected hostname for server to verify against. If server doesn't have
specific whitelisted certificates for client, don't require client to
send certificate at all. */
const bool no_verification = ssl_context.allow_any_cert ||
(type == boost::asio::ssl::stream_base::server && ssl_context.allowed_fingerprints.empty() && ssl_context.ca_path.empty());
/* According to OpenSSL documentation (and SSL specifications), server must
always send certificate unless "anonymous" cipher mode is used which are
disabled by default. Either way, the certificate is never inspected. */
if (no_verification)
socket.set_verify_mode(boost::asio::ssl::verify_none);
else
{ {
// preverified means it passed system or user CA check. System CA is never loaded socket.set_verify_mode(boost::asio::ssl::verify_peer);
// when fingerprints are whitelisted. socket.set_verify_callback([&](bool preverified, boost::asio::ssl::verify_context &ctx)
if (!preverified && !ssl_context.allow_any_cert && !is_certificate_allowed(ctx, ssl_context)) { {
MERROR("Certificate is not in the allowed list, connection droppped"); // preverified means it passed system or user CA check. System CA is never loaded
return false; // when fingerprints are whitelisted.
} if (!preverified && !is_certificate_allowed(ctx, ssl_context)) {
verified = true; MERROR("Certificate is not in the allowed list, connection droppped");
return true; return false;
}); }
verified = true;
return true;
});
}
boost::system::error_code ec; boost::system::error_code ec;
socket.handshake(type, ec); socket.handshake(type, ec);
@ -322,7 +337,7 @@ bool ssl_handshake(boost::asio::ssl::stream<boost::asio::ip::tcp::socket> &socke
MERROR("handshake failed, connection dropped: " << ec.message()); MERROR("handshake failed, connection dropped: " << ec.message());
return false; return false;
} }
if (!ssl_context.allow_any_cert && !verified) if (!no_verification && !verified)
{ {
MERROR("Peer did not provide a certificate in the allowed list, connection dropped"); MERROR("Peer did not provide a certificate in the allowed list, connection dropped");
return false; return false;