A little Googling reveals that this problem is caused by outdated libraries
on the FTP server. The "set_ciphers" option requests than an older, less
secure, protocol be used on the client side in order to match what the
server has.

We could add support for setting cipher levels, but, before doing that, is
there any way you can talk your service provider into updating their
libraries? It's the better approach.

On Sun, Jun 26, 2022 at 12:45 AM Remy Lavabre <[email protected]>
wrote:

> Hello,
> I would like to use WeeWX's FTP option.
> In Python, this works perfectly (WITH THE OPTION IN BOLD) :
>
>
> from ftplib import FTP_TLS
> import ssl
> import requests
>
> HOST='A'
> ID = 'B'
> MDP = 'C'
>
> def connect():
>     ftp = FTP_TLS()
>     ftp.debugging = 2
> *    ftp.context.set_ciphers('DEFAULT@SECLEVEL=1')*
>     ftp.connect(HOST)
>     ftp.login(ID, MDP)
>     return ftp
>
> ftp = connect()
> ftp.retrlines('LIST')
>
> Without this option ' * ftp.context.set_ciphers('DEFAULT@SECLEVEL=1')'*,
> I always get the error: ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too
> small (_ssl.c:997)
>
> *My question*: How to configure the FTPS option in weewx.conf to force
> the same configuration?
> Thanks a lot
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/74de0d09-fe98-4dc4-956a-0dd359f37bd4n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/74de0d09-fe98-4dc4-956a-0dd359f37bd4n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEA2W8MBPEtcnmfWCrEJwrpzD97%3DRsehdrKga6g0Gu3Ktw%40mail.gmail.com.

Reply via email to