forked from xrootd/xrootd
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #18 from stfc/v5.7.1
V5.7.1
- Loading branch information
Showing
142 changed files
with
2,524 additions
and
1,342 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
# | ||
# For a list of checks, run clang-tidy -checks=* --list-checks | ||
# or see https://clang.llvm.org/extra/clang-tidy/checks/list.html | ||
# | ||
--- | ||
Checks: '-*,clang-analyzer-core.*' | ||
WarningsAsErrors: '' | ||
HeaderFilterRegex: '' | ||
FormatStyle: none | ||
CheckOptions: | ||
modernize-use-nullptr.NullMacros: 'NULL' | ||
... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,58 @@ | ||
name: COV | ||
|
||
on: | ||
push: | ||
branches: | ||
- devel | ||
- master | ||
paths-ignore: | ||
- .gitignore | ||
- .gitlab-ci.yml | ||
- .mailmap | ||
- '**.md' | ||
- 'docs/**' | ||
- 'docker/**' | ||
tags: | ||
pull_request: | ||
workflow_dispatch: | ||
|
||
concurrency: | ||
group: ${{ github.workflow }}-${{ github.ref }} | ||
cancel-in-progress: true | ||
|
||
defaults: | ||
run: | ||
shell: bash | ||
|
||
env: | ||
CDASH: ${{ vars.CDASH }} | ||
DEBIAN_FRONTEND: noninteractive | ||
|
||
jobs: | ||
coverage: | ||
name: Coverage Report | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- name: Install dependencies | ||
run: | | ||
sudo ln -sf /usr/share/zoneinfo/UTC /etc/localtime | ||
sudo apt update -q | ||
sudo apt install -y build-essential devscripts equivs gcovr git | ||
- name: Checkout repository | ||
uses: actions/checkout@v4 | ||
with: | ||
fetch-depth: 0 | ||
|
||
- name: Install XRootD build dependencies | ||
run: mk-build-deps --install --remove -s sudo debian/control <<< yes | ||
|
||
- name: Build and Test with CTest | ||
run: ctest -V --output-on-failure -C Debug -DCOVERAGE=1 -S test.cmake | ||
|
||
- if: ${{ vars.CODECOV == 'true' }} | ||
name: Upload coverage to Codecov | ||
uses: codecov/codecov-action@v4 | ||
with: | ||
token: ${{ secrets.CODECOV_TOKEN }} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,73 @@ | ||
# XRootD Security and Vulnerability Disclosure | ||
|
||
This page describes the XRootD security policy and vulnerability | ||
disclosure information. | ||
|
||
## Report a Vulnerability | ||
|
||
We are extremely grateful for security researchers and users that report | ||
vulnerabilities in XRootD. All reports are thoroughly investigated by | ||
the XRootD development team. | ||
|
||
There are two options to report a security vulnerability in XRootD: | ||
|
||
- Directly on GitHub, at https://github.com/xrootd/xrootd/security | ||
- Via email, to the responsible people listed in our website at | ||
http://xrootd.org/contact.html | ||
|
||
Please include in your report a description of the vulnerability, along | ||
with the details expected for regular bug reports, such as the affected | ||
XRootD version, relevant configuration directives, sample log files, etc. | ||
|
||
### When Should I Report a Vulnerability? | ||
|
||
- You think you discovered a potential security vulnerability in XRootD | ||
or in one of the projects that XRootD depends on | ||
|
||
### When Should I NOT Report a Vulnerability? | ||
|
||
- You need help configuring XRootD authentication or security plugins | ||
- You need help applying security related updates | ||
- Your issue is not related to security | ||
|
||
## Security Policy | ||
|
||
### Security Vulnerability Response | ||
|
||
Each report shall be acknowledged and analyzed within 3 working days. | ||
This does not mean that a fix will be available within 3 days, but that | ||
a confirmation of receipt and an assessment of whether or not XRootD is | ||
affected by the vulnerability will be provided within this time frame. | ||
|
||
Any vulnerability information shared with the development team stays | ||
within the collaboration and will not be disseminated to other projects | ||
unless it is necessary to get the issue fixed. | ||
|
||
The reporter of a vulnerability will be kept up to date on progress as | ||
the security issue moves from triage, to identified fix, to release | ||
planning. | ||
|
||
### Public Disclosure Timing | ||
|
||
A public disclosure date is negotiated by the bug submitter and the | ||
XRootD development team. We prefer to fully disclose the bug as soon as | ||
possible once a mitigation is available. It is reasonable to delay | ||
disclosure when the bug or the fix are not yet fully understood, the | ||
solution is not well-tested, or for coordination to get the issue fixed. | ||
The time frame for disclosure is from immediate (especially if it's | ||
already publicly known) to a few weeks. For a vulnerability with a | ||
straightforward mitigation, we expect report date to disclosure date to | ||
be on the order of 1 week. The XRootD collaboration reserves the right | ||
to set a disclosure date based on all the factors as described above. | ||
|
||
## Security Announcements | ||
|
||
Security advisories will be published on the official repository on | ||
GitHub, at https://github.com/xrootd/xrootd/security. Announcements | ||
related to XRootD security will also be sent to the same recipients | ||
used for release announcements, including xrootd-l@slac.stanford.edu. | ||
If you would like to receive security announcements but do not want | ||
to subscribe to our users' mailing list, please use the contact page | ||
above to ask to be included in the list of recipients for security | ||
announcements. Instructions for subscribing to the users' mailing | ||
list can also be found on the contact page. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.