Closed eleaner closed 5 months ago
You can use packet capturing to confirm whether the traffic is encrypted.
I am not sure I know how to do it, but should it be encrypted? and why the dashboard say false?
@fatedier
Ok, so I generated all the keys and certificates, set them up on the server, forced encryption, and set them up on the client.
Proxies are connected but the dashboard still says encryption = false.
I tried to set transport.useEncryption
but the option does not seem to be recognised for http proxies. An example toml has it only on ssh.
transport.useEncryption
work with http?@xqzr Thank you, but I don't think it clearly answers my quesitons
Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
I did not know how to check it so I generated certificates to be 100% sure my traffic is encrypted
On Wed, 3 Apr 2024 at 01:34, notifications at github.com < @.***> wrote:
Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
— Reply to this email directly, view it on GitHub https://github.com/fatedier/frp/issues/4053#issuecomment-2033338158, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHOAM5GJSUZR3TUHJBHB53Y3NE75AVCNFSM6AAAAABERGQRQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTGMZTQMJVHA . You are receiving this because you authored the thread.Message ID: @.***>
I did not know how to check it so I generated certificates to be 100% sure my traffic is encrypted … On Wed, 3 Apr 2024 at 01:34, notifications at github.com < @.> wrote: Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close. — Reply to this email directly, view it on GitHub <#4053 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHOAM5GJSUZR3TUHJBHB53Y3NE75AVCNFSM6AAAAABERGQRQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTGMZTQMJVHA . You are receiving this because you authored the thread.Message ID: @.>
Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Bug Description
From version 0.50 tls encryption should be globally on by default it is not specifically called in the server config file (still frps.ini format) encryption is also not mentioned in the client config
but the dashboard reports encryption=false
does it mean that my frp communicates all in cleartext? I did not generate certificates. do I have to do it specifically?
frpc Version
0.54.0
frps Version
0.52.3
System Architecture
linux/amd64
Configurations
frps.ini
frpc.toml
Logs
none
Steps to reproduce
...
Affected area