Releases: fatedier/frp
Releases · fatedier/frp
v0.53.2
v0.53.0
Features
- The new command line parameter
--strict_config
has been added to enable strict configuration validation mode. It will throw an error for unknown fields instead of ignoring them. In future versions, we will set the default value of this parameter to true to avoid misconfigurations. - Support
SSH reverse tunneling
. With this feature, you can expose your local service without running frpc, only using SSH. The SSH reverse tunnel agent has many functional limitations compared to the frpc agent. The currently supported proxy types are tcp, http, https, tcpmux, and stcp. - The frpc tcpmux command line parameters have been updated to support configuring
http_user
andhttp_pwd
. - The frpc stcp/sudp/xtcp command line parameters have been updated to support configuring
allow_users
.
Fixes
- frpc: Return code 1 when the first login attempt fails and exits.
- When auth.method is
oidc
and auth.additionalScopes containsHeartBeats
, if obtaining AccessToken fails, the application will be unresponsive.
v0.52.3
v0.52.2
v0.52.1
v0.52.0
Features
- Configuration: We now support TOML, YAML, and JSON for configuration. Please note that INI is deprecated and will be removed in future releases. New features will only be available in TOML, YAML, or JSON. Users wanting these new features should switch their configuration format accordingly. #2521
Breaking Changes
- Change the way to start the visitor through the command line from
frpc stcp --role=visitor xxx
tofrpc stcp visitor xxx
. - Modified the semantics of the
server_addr
in the command line, no longer including the port. Added theserver_port
parameter to configure the port. - No longer support range ports mapping in TOML/YAML/JSON.
v0.51.3
v0.51.2
v0.51.1
v0.51.0
Features
- frpc supports connecting to frps via the wss protocol by enabling the configuration
protocol = wss
. - frpc supports stopping the service through the stop command.
Improvements
- service.Run supports passing in context.
Fixes
- Fix an issue caused by a bug in yamux that prevents wss from working properly in certain plugins.