Starting now, any publicly dialable Kubo node with a /tcp listener that remains online for at least one hour will receive a TLS certificate through the AutoTLS feature.
This occurs automatically, with no need for manual setup.
To bypass the 1-hour delay and enable AutoTLS immediately, users can explicitly opt-in by running the following commands:
$ ipfs config --json AutoTLS.Enabled true
$ ipfs config --json AutoTLS.RegistrationDelay 0AutoTLS will remain disabled under the following conditions:
- The node already has a manually configured
/ws(WebSocket) listener - A private network is in use with a
swarm.key - TCP or WebSocket transports are disabled, or there is no
/tcplistener
To troubleshoot, use GOLOG_LOG_LEVEL="error,autotls=info.
For more details, check out the AutoTLS configuration documentation or dive deeper with AutoTLS libp2p blog post.
ipfs configis now validating json fields (#10679).- Deprecated the
bitswap reprovidecommand. Make sure to switch to modernrouting reprovide. (#10677) - The
stats reprovidecommand now shows additional stats forRouting.AcceleratedDHTClient, indicating the last and nextreprovidetimes. (#10677) ipfs files cpnow performs basic codec check and will error when source is not a valid UnixFS (onlydag-pbandrawcodecs are allowed in MFS)
This release includes performance and reliability improvements and fixes for minor resource leaks. One of the performance changes greatly improves the bitswap clients ability to operate under high load, that could previously result in an out of memory condition.
The variable has been deprecated. Please use GOLOG_LOG_LEVEL instead for configuring logging levels.
If the pebble database format is not explicitly set in the config, then automatically upgrade it to the latest format version supported by the release ob pebble used by kubo. This will ensure that the database format is sufficiently up-to-date to be compatible with a major version upgrade of pebble. This is necessary before upgrading to use pebble v2.
An update was made to the badger v1 datastore that avoids use of mmap in 32-bit environments, which has been seen to cause issues on some platforms. Please be aware that this could lead to a performance regression for users of badger in a 32-bit environment. Badger users are advised to move to the flatds or pebble datastore.
The go-ds-xxx datastore implementations have been updated to support the updated go-datastore v0.8.2 query API. This update removes the datastore implementations' dependency on goprocess and updates the query API.
Kubo previously depended on multiple multi-error packages, github.com/hashicorp/go-multierror and go.uber.org/multierr. These have nearly identical functionality so there was no need to use both. Therefore, go.uber.org/multierr was selected as the package to depend on. Any future code needing multi-error functionality should use go.uber.org/multierr to avoid introducing unneeded dependencies.