Option to not verify SSL Certificate for RSS Feed #9126

Closed
opened 2025-12-29 20:45:59 +01:00 by adam · 3 comments
Owner

Originally created by @YoucefYousfi on GitHub (Jan 22, 2024).

NetBox version

v3.7.1

Feature type

Change to existing functionality

Proposed functionality

For the RSS Feed, adding the option of not verifying the SSL Certificate.
In UI : a checkbox to add "verify=False" option to the rss feed request
In default dashboard configuration : a simple verify=False line added

Use case

This would allow users to use unverified URLs for RSS Feeds optionally.

Database changes

No response

External dependencies

No response

Originally created by @YoucefYousfi on GitHub (Jan 22, 2024). ### NetBox version v3.7.1 ### Feature type Change to existing functionality ### Proposed functionality For the RSS Feed, adding the option of not verifying the SSL Certificate. In UI : a checkbox to add "verify=False" option to the rss feed request In default dashboard configuration : a simple verify=False line added ### Use case This would allow users to use unverified URLs for RSS Feeds optionally. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:45:59 +01:00
adam closed this issue 2025-12-29 20:46:00 +01:00
Author
Owner

@DanSheps commented on GitHub (Jan 23, 2024):

This would allow users to use unverified URLs for RSS Feeds optionally.

I think an additional use case might be to allow a MitM for things like corporate firewalls without having to load and maintain the certificate (although you should IMO)

@DanSheps commented on GitHub (Jan 23, 2024): > This would allow users to use unverified URLs for RSS Feeds optionally. I think an additional use case might be to allow a MitM for things like corporate firewalls without having to load and maintain the certificate (although you should IMO)
Author
Owner

@jeremystretch commented on GitHub (Jan 23, 2024):

IMO, as an industry we are by now beyond this. Management of TLS certificates has become so easy and commonplace, there's really no excuse for having an invalid certificate. (I'm aware we have an option on the webhook model to disable certificate validation; I think we should get rid of it.)

@jeremystretch commented on GitHub (Jan 23, 2024): IMO, as an industry we are by now beyond this. Management of TLS certificates has become so easy and commonplace, there's really no excuse for having an invalid certificate. (I'm aware we have an option on the webhook model to disable certificate validation; I think we should get rid of it.)
Author
Owner

@jeremystretch commented on GitHub (Mar 8, 2024):

I'm going to close this out as the proposal pretty starkly violates good security practice.

@jeremystretch commented on GitHub (Mar 8, 2024): I'm going to close this out as the proposal pretty starkly violates good security practice.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9126