perfsonar / perfsonar/toolkit

Restructure perfsonar-toolkit-security package

Open
#382 2 comments 0 reactions 1 assignee View on GitHub

@arlake228 is already working on this.

Since May 29, 2019.

Dominant language
JavaScript
Stars
37
Forks
7
PR merge metrics
No merged PRs in 30d

Description

It was decided we would like to further breakout the perfsonar-toolkit-security package instead more packages (maybe without toolkit in the name) that represent the individual functions so it is not all or nothing. This would give users more flexibility and make it easier for Ansible to manage firewalls. We probably ant packages for the following:

  • open http(s)-related ports (i.e. esmond, pscheduler, maddash)
  • open individual tool ports (OWAMP, iperf3, etc)
  • Configure apache (and maybe an extra secure version for federal users)
  • Configure memcached security
  • Set up fail2ban

Will need to finalize how we organize these and may think of other things. We can still have a perfsonar-toolkit-security but it will depend on the sub-packages

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.