您好，我必须通过发送FIX消息来设置stunnel（来自stunnel.org）进行加密，即使我已经按照经纪人的说明进行了设置，即使我使用了stunnel，我仍然可以使用Wireshark来拾取和读取消息。似乎运行正常。
我进行了搜索，只找到了一种在Unix上进行测试的方法，但是Windows 10是否有一个好的方法？因为我假设如果可以使用Wireshark读取它，则它将无法正常工作。我在下面提供了我的Stunnel日志，以供参考，感谢您的投入！
感谢阅读！
2018.06.21 13:44:16 LOG7[main]: Running on Windows 6.2
2018.06.21 13:44:16 LOG7[main]: No limit detected for the number of clients
2018.06.21 13:44:16 LOG5[main]: stunnel 5.46 on x86-pc-msvc-1500 platform
2018.06.21 13:44:16 LOG5[main]: Compiled/running with OpenSSL 1.0.2o-fips 27 Mar 2018
2018.06.21 13:44:16 LOG5[main]: Threading:WIN32 Sockets:SELECT,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI
2018.06.21 13:44:16 LOG7[main]: errno: (*_errno())
2018.06.21 13:44:16 LOG7[ui]: GUI message loop initialized
2018.06.21 13:44:16 LOG7[main]: Running on Windows 6.2
2018.06.21 13:44:16 LOG5[main]: Reading configuration from file stunnel.conf
2018.06.21 13:44:16 LOG5[main]: UTF-8 byte order mark detected
2018.06.21 13:44:16 LOG5[main]: FIPS mode disabled
2018.06.21 13:44:16 LOG7[main]: Compression disabled
2018.06.21 13:44:16 LOG7[main]: No PRNG seeding was required
2018.06.21 13:44:16 LOG6[main]: Initializing service [FEED_FIX_BRIDGE]
2018.06.21 13:44:16 LOG7[main]: Ciphers: ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-DSS-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDH-RSA-AES256-GCM-SHA384:ECDH-ECDSA-AES256-GCM-SHA384:AES256-GCM-SHA384:DHE-RSA-AES256-SHA:DHE-DSS-AES256-SHA:AES256-SHA
2018.06.21 13:44:16 LOG7[main]: TLS options: 0x03000004 (+0x03000000, -0x00000000)
2018.06.21 13:44:16 LOG7[main]: No certificate or private key specified
2018.06.21 13:44:16 LOG4[main]: Service [FEED_FIX_BRIDGE] uses "verifyChain" without subject checks
2018.06.21 13:44:16 LOG4[main]: Use "checkHost" or "checkIP" to restrict trusted certificates
2018.06.21 13:44:16 LOG6[main]: Initializing service [BROKER_FIX_BRIDGE]
2018.06.21 13:44:16 LOG7[main]: Ciphers: ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-DSS-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDH-RSA-AES256-GCM-SHA384:ECDH-ECDSA-AES256-GCM-SHA384:AES256-GCM-SHA384:DHE-RSA-AES256-SHA:DHE-DSS-AES256-SHA:AES256-SHA
2018.06.21 13:44:16 LOG7[main]: TLS options: 0x03000004 (+0x03000000, -0x00000000)
2018.06.21 13:44:16 LOG7[main]: No certificate or private key specified
2018.06.21 13:44:16 LOG4[main]: Service [BROKER_FIX_BRIDGE] uses "verifyChain" without subject checks
2018.06.21 13:44:16 LOG4[main]: Use "checkHost" or "checkIP" to restrict trusted certificates
2018.06.21 13:44:16 LOG5[main]: Configuration successful
2018.06.21 13:44:16 LOG7[main]: Binding service [FEED_FIX_BRIDGE]
2018.06.21 13:44:16 LOG7[main]: Listening file descriptor created (FD=792)
2018.06.21 13:44:16 LOG7[main]: Setting accept socket options (FD=792)
2018.06.21 13:44:16 LOG7[main]: Option SO_EXCLUSIVEADDRUSE set on accept socket
2018.06.21 13:44:16 LOG6[main]: Service [FEED_FIX_BRIDGE] (FD=792) bound to 127.0.0.1:8100
2018.06.21 13:44:16 LOG7[main]: Binding service [BROKER_FIX_BRIDGE]
2018.06.21 13:44:16 LOG7[main]: Listening file descriptor created (FD=796)
2018.06.21 13:44:16 LOG7[main]: Setting accept socket options (FD=796)
2018.06.21 13:44:16 LOG7[main]: Option SO_EXCLUSIVEADDRUSE set on accept socket
2018.06.21 13:44:16 LOG6[main]: Service [BROKER_FIX_BRIDGE] (FD=796) bound to 127.0.0.1:8101
2018.06.21 13:44:16 LOG7[cron]: Cron thread initialized
2018.06.21 13:45:16 LOG6[cron]: Executing cron jobs
2018.06.21 13:45:16 LOG6[cron]: Cron jobs completed in 0 seconds
2018.06.21 13:45:16 LOG7[cron]: Waiting 86400 seconds