mirror of
https://github.com/ramsayleung/rspotify.git
synced 2026-04-26 16:05:53 +03:00
[PR #476] [MERGED] security: Disable TLS1.0/1.1 for ureq-native-tls #482
Labels
No labels
Stale
bug
discussion
enhancement
good first issue
good first issue
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rspotify#482
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/ramsayleung/rspotify/pull/476
Author: @Property404
Created: 4/3/2024
Status: ✅ Merged
Merged: 4/9/2024
Merged by: @ramsayleung
Base:
master← Head:Property404/dont_use_old_tls📝 Commits (1)
0d42dcasecurity: Disable TLS1.0/1.1 for ureq-native-tls📊 Changes
1 file changed (+5 additions, -1 deletions)
View changed files
📝
rspotify-http/src/ureq.rs(+5 -1)📄 Description
Description
Explicity opt-out of old TLS versions when using the ureq-native-tls feature. Rust-native-tls enables these outdated TLS versions by default
Motivation and Context
TLS 1.0 and 1.1 have been deprecated since 2021. Enabling TLS 1.0/1.1 has possibility (albeit a low one) of introducing a security vulnerability. All modern clients and servers have supported 1.2 for years, so this should be an issue
Dependencies
None
Type of change
How has this been tested?
Locally only, through cargo-test and cargo-clippy
Is this change properly documented?
Added a short comment explaining reasoning
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.