Working out issues with SSL termination via loadbalancers for electrum-dash-server
I see it appears that electrum-dash requires SSLv3 - because poodle (vulnerability) , this is less supported in general (though it's clearly supported in the electrum-dash server itself.
Encompass correctly connects to either port, while electrum-dash will not verify the cert on the LB-termination.
Electrum-Dash should probably not require SSLv3
cc @Kefkius
electrum-dash.maza.club:50001:t
electrum-dash.maza.club:50002:s < pass through
electrum-dash.maza.club:50003:s < LB SSL termination
electrum.maza.club:50008:s << LB termination
electurm-dash.maza.club:50006:s << bypass LB
[Edit: correclt port on electrum.maza.club] add a few more
Default cert to get is electrum-dash.mazaclub - port 50008 serves electrum.maza.club
Working out issues with SSL termination via loadbalancers for electrum-dash-server
I see it appears that electrum-dash requires SSLv3 - because poodle (vulnerability) , this is less supported in general (though it's clearly supported in the electrum-dash server itself.
In the configurations:
E-Dash -> LB (TCP Passthrough) -> Electrum-Dash-Server:SSL
E-Dash -> LB SSL Termination -> Electrum-Dash-Server-TCP
Encompass correctly connects to either port, while electrum-dash will not verify the cert on the LB-termination.
Electrum-Dash should probably not require SSLv3
cc @Kefkius
electrum-dash.maza.club:50001:t electrum-dash.maza.club:50002:s < pass through electrum-dash.maza.club:50003:s < LB SSL termination electrum.maza.club:50008:s << LB termination electurm-dash.maza.club:50006:s << bypass LB [Edit: correclt port on electrum.maza.club] add a few more
Default cert to get is electrum-dash.mazaclub - port 50008 serves electrum.maza.club