I'm ok with it not being optional (although even zeus allows to not provide one!), but i would like it to at least accept the self signed tls.cert of my LND node. Right now, this gitves a 'self signed' error in the SN logs, and my LND node gets the similar error that remote rejected it.


There's probably no risk for SN, the risk is more that the connection is not ecrypted end-to-end and could attract malicious attacks.

Not really sure about the technicalities or risks on leaving it empty, as is an optional feature.

Maybe @k00b @ek able to provide more info

supratic

Is there a real reason to not accept self signed certificate of LND instead of having to provide a 'trusted' one?

I mean, worst case, if I did not give a safe certificate, AND some one spoofed my node's IP, they would receive my zaps.  I should be able to accept that risk?

There's no real risk for SN, or is there?

lightning

How to attach your LND node to RECEIVE bitcoin from SN via ThunderHub

Is there a real reason to not accept self signed certificate of LND instead of having to provide a 'trusted' one?

I mean, worst case, if I did not give a safe certificate, AND some one spoofed my node's IP, they would receive my zaps.  I should be able to accept that risk?

There's no real risk for SN, or is there?
