Security - Revision history

Pjones at 13:43, 3 May 2026

2026-05-03T13:43:42Z

← Older revision		Revision as of 06:43, 3 May 2026
Line 1:		Line 1:
	If you have details of a suspected security vulnerability in Lustre code that you wish to report then please [mailto:security@~~whamcloud~~.com email us at security@~~whamcloud~~.com] with the details.		If you have details of a suspected security vulnerability in Lustre code that you wish to report then please [mailto:security@thelustrecollective.com email us at security@thelustrecollective.com] with the details.

	Please do not file a public JIRA issue for a security vulnerability - we do not want to draw attention to the vulnerability until a fix has been developed and administrators have been alerted and have had some time to put a mitigation in place.		Please do not file a public JIRA issue for a security vulnerability - we do not want to draw attention to the vulnerability until a fix has been developed and administrators have been alerted and have had some time to put a mitigation in place.

Pjones: Protected "Security" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2024-02-09T13:15:22Z

Protected "Security" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision

Revision as of 06:15, 9 February 2024

Adilger: minor edits

2024-02-09T04:09:11Z

minor edits

← Older revision		Revision as of 21:09, 8 February 2024
Line 1:		Line 1:
	If you have details of a suspected security vulnerability in Lustre code that you wish to report then please [mailto:security@whamcloud.com email us] with the details.		If you have details of a suspected security vulnerability in Lustre code that you wish to report then please [mailto:security@whamcloud.com email us at security@whamcloud.com] with the details.

	Please do not file a public JIRA issue for a vulnerability - we do not want to draw attention to the vulnerability until ~~users~~ have been alerted and have had some time to put a mitigation in place.		Please do not file a public JIRA issue for a security vulnerability - we do not want to draw attention to the vulnerability until a fix has been developed and administrators have been alerted and have had some time to put a mitigation in place.

	Ideally the reporting email should have as much detail as possible:		Ideally the reporting email should have as much detail as possible:
Line 10:		Line 10:
	* your intentions around disclosing the details of the vulnerability		* your intentions around disclosing the details of the vulnerability

	We aim to respond to any such reports within three days of receipt.		We aim to respond to any such reports within three business days of receipt.

Pjones at 00:19, 9 February 2024

2024-02-09T00:19:57Z

← Older revision		Revision as of 17:19, 8 February 2024
Line 5:		Line 5:
	Ideally the reporting email should have as much detail as possible:		Ideally the reporting email should have as much detail as possible:

	-reproducer, versions affected, fix if available, etc.		* reproducer, versions affected, fix if available, etc.
	-indicate to whom (individual and/or affiliation) that credit for finding the issue should be reported		* indicate to whom (individual and/or affiliation) that credit for finding the issue should be reported
	-details of any CVE already reserved		* details of any CVE already reserved
	-your intentions around disclosing the details of the vulnerability		* your intentions around disclosing the details of the vulnerability

	We aim to respond to any such reports within three days of receipt.		We aim to respond to any such reports within three days of receipt.

Pjones at 00:19, 9 February 2024

2024-02-09T00:19:20Z

← Older revision		Revision as of 17:19, 8 February 2024
Line 1:		Line 1:
	If you have details of a suspected security vulnerability in Lustre code that you wish to report then please [mailto:security@whamcloud.com email us] with the details.		If you have details of a suspected security vulnerability in Lustre code that you wish to report then please [mailto:security@whamcloud.com email us] with the details.

			Please do not file a public JIRA issue for a vulnerability - we do not want to draw attention to the vulnerability until users have been alerted and have had some time to put a mitigation in place.

			Ideally the reporting email should have as much detail as possible:

			-reproducer, versions affected, fix if available, etc.
			-indicate to whom (individual and/or affiliation) that credit for finding the issue should be reported
			-details of any CVE already reserved
			-your intentions around disclosing the details of the vulnerability

			We aim to respond to any such reports within three days of receipt.

Pjones: Created page with "If you have details of a suspected security vulnerability in Lustre code that you wish to report then please [mailto:security@whamcloud.com email us] with the details."

2023-05-26T17:43:30Z

Created page with "If you have details of a suspected security vulnerability in Lustre code that you wish to report then please [mailto:security@whamcloud.com email us] with the details."

New page

If you have details of a suspected security vulnerability in Lustre code that you wish to report then please [mailto:security@whamcloud.com email us] with the details.