Author: joewitt
Date: Tue Feb 8 19:24:27 2022
New Revision: 1897878
URL: http://svn.apache.org/viewvc?rev=1897878&view=rev
Log:
fds, registry, security, and apache nifi slack updates
Modified:
nifi/site/trunk/fds-release-guide.html
nifi/site/trunk/fds.html
nifi/site/trunk/mailing_lists.html
nifi/site/trunk/registry-security.html
nifi/site/trunk/security.html
Modified: nifi/site/trunk/fds-release-guide.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/fds-release-guide.html?rev=1897878&r1=1897877&r2=1897878&view=diff
==============================================================================
--- nifi/site/trunk/fds-release-guide.html (original)
+++ nifi/site/trunk/fds-release-guide.html Tue Feb 8 19:24:27 2022
@@ -177,7 +177,7 @@ ${NIFI_FDS_VERSION} 0.1.0
${NEXT_VERSION} 0.2.0-SNAPSHOT the future version for development on
the release branch.<br>
${JIRA_TICKET} NIFI-2112 the JIRA ticket created by the
release manager for the release tasks.<br>
${RC} 2 the Release Candidate index start at
1 for the first release candidate.<br>
-${RC_TAG_COMMIT_ID} the 40 byte commit ID of the RC tag
created during the Maven release process.<br>
+${RC_TAG_COMMIT_ID} the 40 byte commit ID of the RC tag
created during the release process.<br>
${RM_USERID} johndoe the Apache account ID of Release
Manager.<br>
${RELEASE_TAG} rel/nifi-0.7.0 the Git repository tag for the source
code as released.<br>
${VOTE_THREAD_URL} <a
href="https://lists.apache.org/thread.html/07156f3a773841ba1e27f2c89bb5fd57698cb5e3eae000c12bb593b5@%3Cdev.nifi.apache.org%3E";>0.1.0
vote thread</a> the URL for the Apache Pony Mail archive of the release vote
thread.<br>
@@ -246,48 +246,46 @@ acceptable but the appropriate adjustmen
<li>Create meaningful release notes for this version if not already created.
<a href="https://cwiki.apache.org/confluence/display/NIFI/Release+Notes";>Enter
them here</a> on<br>
the NiFi wiki.</li>
<li>Create a new branch off 'main' named after the JIRA ticket.
-<pre><code class="language-bash">$ git checkout -b
NIFI-FDS-${JIRA_TICKET}-RC${RC} ${BRANCH}
+<pre><code class="language-bash">$ git checkout -b
NIFI-FDS-${NIFI_FDS_VERSION}-RC${RC} ${BRANCH}
</code></pre></li>
<li>Ensure the the full application builds and all tests work by executing a
build.
<pre><code>$ npm run clean:install
</code></pre></li>
<li>Startup and test the demo application from the target source folder.
After a few seconds, NiFi FDS should be up and<br>
running at <a href="http://localhost:8080";>http://localhost:8080</a>.
-<pre><code>$ cd target/
+<pre><code>$ cd target/frontend-working-directory
$ npm start
</code></pre></li>
<li>Evaluate and ensure the appropriate license headers are present on all
source files.</li>
<li>Ensure LICENSE and NOTICE files are complete and accurate. (Developers
should always be keeping these up to date as<br>
they go along adding source and modifying dependencies to keep this burden
manageable.)</li>
+<li>Verify that no vulnerabilities exist in any javascript module dependencies
(requires npm 6+).
+<pre><code>$ npm audit
+</code></pre></li>
</ol>
<h3>Step 3. Perform the release (RM)</h3>
<ol>
-<li>Now its time to prepare the release. Manually update the version number
in</li>
-</ol>
+<li><p>Now it's time to prepare the release. Manually update the version
number in</p>
<ul>
<li>root package.json</li>
<li>root package-lock.json</li>
<li>src/platform/core/package.json</li>
-</ul>
-<ol>
+</ul></li>
<li><p>Zip up the source.</p>
-<pre><code>$ git archive --format zip --prefix=nifi-fds-${NIFI_FDS_VERSION}/
NIFI-FDS-${NIFI_FDS_VERSION}-RC${RC}
+<pre><code>$ git archive --format=zip --prefix=nifi-fds-${NIFI_FDS_VERSION}/
NIFI-FDS-${NIFI_FDS_VERSION}-RC${RC} > nifi-fds-0.2.0-source-release.zip
</code></pre></li>
<li><p>Create the tag.</p>
<pre><code>$ git tag NIFI-FDS-${NIFI_FDS_VERSION}-RC${RC}
</code></pre></li>
<li><p>Push the release branch to the ASF repository.</p>
-<pre><code>$ git push asf NIFI-FDS-${JIRA_TICKET}-RC${RC} --tags
+<pre><code>$ git push asf NIFI-FDS-${NIFI_FDS_VERSION}-RC${RC} --tags
</code></pre>
-<p><strong><em>From this branch, the ${RC_TAG_COMMIT_ID} will be the 40 byte
commit hash with the comment NIFI-FDS-${JIRA_TICKET}-RC${RC} prepare release
nifi-fds-${NIFI_FDS_VERSION}-RC${RC}</em></strong></p></li>
-<li><p>Create the signature and hashes for the source release and convenience
binary files.</p>
+<p><strong><em>From this branch, the ${RC_TAG_COMMIT_ID} will be the 40 byte
commit hash with the comment NIFI-FDS-${NIFI_FDS_VERSION}-RC${RC} prepare
release nifi-fds-${NIFI_FDS_VERSION}-RC${RC}</em></strong></p></li>
+<li><p>Create the signature and hashes for the source release.</p>
<ol>
<li>ASCII armored GPG signatures (<code>--digest-algo=SHA512</code> select the
SHA512 hash algorithm). <a
href="https://www.apache.org/dev/openpgp.html#key-gen-avoid-sha1";>Configure GPG
to always prefer stronger hashes</a>.
<pre><code>$ gpg -a -b --digest-algo=SHA512
nifi-fds-${NIFI_FDS_VERSION}-source-release.zip # produces
nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.asc
</code></pre></li>
-<li>Generate SHA1 hash summaries.
-<pre><code>$ shasum -a 1 nifi-fds-${NIFI_FDS_VERSION}-source-release.zip | cut
-d" " -f1 > nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.sha1
-</code></pre></li>
<li>Generate SHA256 hash summaries.
<pre><code>$ shasum -a 256 nifi-fds-${NIFI_FDS_VERSION}-source-release.zip |
cut -d" " -f1 >
nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.sha256
</code></pre></li>
@@ -295,7 +293,20 @@ they go along adding source and modifyin
<pre><code>$ shasum -a 512 nifi-fds-${NIFI_FDS_VERSION}-source-release.zip |
cut -d" " -f1 >
nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.sha512
</code></pre></li>
</ol></li>
-<li><p>Commit the source release along with their hashes and signatures to
<code>https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}</code>.</p></li>
+<li><p>Commit the source release along with their hashes and signatures to
<code>https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}</code>.</p>
+<ol>
+<li>Checkout the Apache dist dev svn repo locally using your Apache credentials
+<pre><code>$ svn checkout https://dist.apache.org/repos/dist/dev/nifi
+</code></pre></li>
+<li>Create the directory for nifi-fds-${NIFI_FDS_VERSION}.</li>
+<li>Copy the zipped source release and its corresponding signatures and hashes
into the new directory.</li>
+<li>Add the commit.
+<pre><code>$ svn add ./nifi-fds-${NIFI_FDS_VERSION}/*
+</code></pre></li>
+<li>Stage the artifacts by committing to svn.
+<pre><code>$ svn commit -m 'Staging artifacts for nifi-fds-${NIFI_FDS_VERSION}'
+</code></pre></li>
+</ol></li>
</ol>
<h3>Step 4. Error recovery (RM)</h3>
<p>If anything isn't correct about the staged artifacts you can delete<br>
@@ -320,7 +331,7 @@ and more positive than negative binding
I am pleased to be calling this vote for the source release of Apache NiFi
Flow Design System nifi-fds-${NIFI_FDS_VERSION}.
The source zip, including signatures, etc. can be found at:
-https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}
+https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}
The Git tag is nifi-${NIFI_FDS_VERSION}-RC${RC}
The Git commit ID is ${RC_TAG_COMMIT_ID}
@@ -368,11 +379,11 @@ https://dist.apache.org/repos/dist/dev/n
gpg --import KEYS
# Pull down nifi-fds-${NIFI_FDS_VERSION} source release artifacts for review:
-wget
https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}/nifi-fds-${NIFI_FDS_VERSION}-source-release.zip
-wget
https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}/nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.asc
-wget
https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}/nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.sha1
-wget
https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}/nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.sha256
-wget
https://dist.apache.org/repos/dist/dev/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}/nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.sha512
+wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}/nifi-fds-${NIFI_FDS_VERSION}-source-release.zip
+wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}/nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.asc
+wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}/nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.sha1
+wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}/nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.sha256
+wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}/nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.sha512
# Verify the signature
gpg --verify nifi-fds-${NIFI_FDS_VERSION}-source-release.zip.asc
@@ -384,7 +395,7 @@ sha512sum nifi-fds-${NIFI_FDS_VERSION}-s
# Unzip nifi-fds-${NIFI_FDS_VERSION}-source-release.zip
-# Verify the build works (npm version >= 5.6.0)
+# Verify the build works
cd nifi-fds-${NIFI_FDS_VERSION}
npm run clean:install
@@ -395,8 +406,8 @@ npm run clean:install
# Verify the RC was branched off the correct git commit ID
# Run the demo-app and make sure it works as expected
-cd target
-npm start
+cd target/frontend-working-directory
+npm run watch
# Make sure the README, NOTICE, and LICENSE are present and correct
cd node_modules/@nifi-fds/core
@@ -435,41 +446,66 @@ Here is the PMC vote thread: ${VOTE_THRE
<h3>Step 6. Finalize the Release</h3>
<p>After the vote is complete and the release is approved, these steps
complete the release process.</p>
<ol>
-<li><p>Move convenience binaries and related artifacts from dist/dev to
dist/release:</p>
-<pre><code>$ svn move -m "NIFI-FDS-${JIRA_TICKET}"
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}
https://dist.apache.org/repos/dist/release/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}
+<li><p>Move the source code and related artifacts from dist/dev to
dist/release:</p>
+<pre><code>$ svn move -m "NIFI-FDS-${NIFI_FDS_VERSION}"
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}
https://dist.apache.org/repos/dist/release/nifi/nifi-fds/nifi-fds-${NIFI_FDS_VERSION}
+</code></pre></li>
+<li><p>Manually update the version number to the next snapshot</p>
+<pre><code class="language-bash">$ git checkout
NIFI-FDS-${NIFI_FDS_VERSION}-RC${RC}
+</code></pre>
+<p>Update the version number to the next
<code>${NIFI_FDS_VERSION}-SNAPSHOT</code> in</p>
+<ul>
+<li>root package.json</li>
+<li>root package-lock.json</li>
+<li>src/platform/core/package.json</li>
+</ul>
+<pre><code class="language-bash">$ git add -A .
+$ git commit -m 'NIFI-FDS-${NIFI_FDS_VERSION} finalize RC${RC}'
</code></pre></li>
<li><p>Merge the release branch into main.</p>
<pre><code>$ git checkout main
-$ git merge --no-ff NIFI-FDS-${JIRA_TICKET}-RC${RC}
+$ git merge --no-ff NIFI-FDS-${NIFI_FDS_VERSION}-RC${RC}
$ git push asf main
</code></pre></li>
<li><p>Publish to the npm registry</p>
-<pre><code>$ npm run publish
+<pre><code>$ cd nifi-fds/target/frontend-working-directory/platform/core
+$ cp -f ../../README.md ./README.md
+$ npm login
+$ npm publish
</code></pre></li>
<li><p>Deploy the gh-pages demo</p>
-<pre><code># switch to gh-pages branch
-$ git remote update
+<p>First, switch to gh-pages branch:</p>
+<pre><code>$ git remote update
$ git checkout gh-pages
$ git reset --hard asf/gh-pages
-
-# simulate npm install of @nifi-fds/core
-$ rm -rf ./node_modules/
-$ mv ./target/node_modules/ ./
-$ rm -rf ./demo-app/
-$ mv ./target/demo-app/ ./
-
-# update base href for github.io page
-$ cp -f ./target/gh-pages.index.html ./index.html
-$ cp -f ./target/README.md ./README.md
-$ git add -A .
-$ git commit -m 'gh-pages update'
+</code></pre>
+<p>Next, simulate npm install of @nifi-fds/core:</p>
+<pre><code>$ rm -rf ./node_modules/
+$ mv ./target/frontend-working-directory/node_modules/ ./
+$ rm -rf ./webapp/
+$ mv ./target/frontend-working-directory/webapp/ ./
+</code></pre>
+<p>Next, update the bundles, index.html, and README for the github.io page:</p>
+<pre><code>$ cp ./target/frontend-working-directory/fds-demo.* .
+$ cp -f ./target/frontend-working-directory/index.html ./index.html
+$ cp -f ./target/frontend-working-directory/README.md ./README.md
+</code></pre>
+<p>Next, start the demo:</p>
+<pre><code>$ ./node_modules/http-server/bin/http-server
+</code></pre>
+<p>Now, test that the demo application runs with the latest updates by
visiting http://127.0.0.1:8080.</p>
+<p>Next, edit the index.html and change the base href to <code><base
href="/nifi-fds/"></code>:</p>
+<pre><code>$ nano ./index.html
+</code></pre>
+<p>and change the base href to <code><base
href="/nifi-fds/"></code>.</p>
+<p>Finally, commit and push the changes:</p>
+<pre><code>$ git add -A .
+$ git commit -m 'NIFI-FDS-${NIFI_FDS_VERSION} gh-pages update demo
application to run NiFi FDS ${NIFI_FDS_VERSION}'
$ git push asf gh-pages:gh-pages
-
</code></pre></li>
<li><p>Update the NiFi Web Page to indicate NEWS of the release as
appropriate</p></li>
-<li><p>In JIRA mark the release version as 'Released' and 'Archived' through
'version' management in the 'administration' console.</p></li>
+<li><p>In JIRA resolve the NIFI-FDS-${JIRA_TICKET} and then mark the release
version as 'Released' and 'Archived' through 'version' management in the
'administration' console. Then create a new version name for the next NiFi FDS
release.</p></li>
<li><p>Create a proper signed tag of the released codebase based on the RC Tag
created during the release process.</p>
-<pre><code>$ git tag -s rel/nifi-fds-${NIFI_FDS_VERSION} -m
"${JIRA_TICKET} signed release tag for approved release of NiFi Flow
Design System ${NIFI_FDS_VERSION}" ${RC_TAG_COMMIT_ID}
+<pre><code>$ git tag -s rel/nifi-fds-${NIFI_FDS_VERSION} -m
"NIFI-FDS-${JIRA_TICKET} signed release tag for approved release of NiFi
Flow Design System ${NIFI_FDS_VERSION}" ${RC_TAG_COMMIT_ID}
</code></pre>
<p>For instructions on setting up to sign your tag see <a
href="http://gitready.com/advanced/2014/11/02/gpg-sign-releases.html";>here</a>.</p></li>
<li><p>Push the release tag to the official ASF repository.</p>
@@ -494,11 +530,11 @@ The Apache NiFi team would like to annou
Apache NiFi Flow Design System is an atomic reusable platform for providing a
consistent set of UI/UX components for open source friendly web applications to
consume.
-More details on Apache NiFi can be found here:
+More details on Apache NiFi Flow Design System can be found here:
https://nifi.apache.org/fds.html
Issues closed/resolved for this list can be found here:
-https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12329373
+https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=${NIFI_FDS_PROJECT_ID}&version=${NIFI_FDS_VERSION_ID}
Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version${NIFI_FDS_VERSION}
Modified: nifi/site/trunk/fds.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/fds.html?rev=1897878&r1=1897877&r2=1897878&view=diff
==============================================================================
--- nifi/site/trunk/fds.html (original)
+++ nifi/site/trunk/fds.html Tue Feb 8 19:24:27 2022
@@ -135,7 +135,7 @@
<div class="row">
<div class="large-12 columns">
<p class="description">
- Flow Design System—a subproject of Apache NiFi— is an
atomic reusable platform for providing a common set of UI/UX components for
Apache NiFi, Apache NiFi Registry, Apache NiFi MiNiFi, and any other open
source web applications to consume.
+ Flow Design System—a subproject of Apache NiFi— is an
atomic reusable platform for providing a consistent set of UI/UX components for
Apache NiFi, Apache NiFi Registry, Apache NiFi MiNiFi, and any other open
source web applications to consume.
</p>
<p class="description">
Specific goals for the initial thrust of the Flow Design System
effort include:
@@ -162,7 +162,49 @@
Releases
<ul>
<li>
- TBD
+ 0.3.0
+ <ul>
+ <li>
+ Sources
+ <ul>
+ <li><a
href="https://www.apache.org/dyn/closer.lua?path=/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip";>nifi-fds-0.3.0-source-release.zip</a>
(
+ <a
href="https://www.apache.org/dist/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.asc";>asc</a>,
+ <a
href="https://www.apache.org/dist/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha256";>sha256</a>,
+ <a
href="https://www.apache.org/dist/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip.sha512";>sha512</a>
)</li>
+ </ul>
+ </li>
+ <li><a
href="https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.0";>Release
Notes</a></li>
+ </ul>
+ </li>
+ <li>
+ 0.2.0
+ <ul>
+ <li>
+ Sources
+ <ul>
+ <li><a
href="https://www.apache.org/dyn/closer.lua?path=/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip";>nifi-fds-0.2.0-source-release.zip</a>
(
+ <a
href="https://www.apache.org/dist/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.asc";>asc</a>,
+ <a
href="https://www.apache.org/dist/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.sha256";>sha256</a>,
+ <a
href="https://www.apache.org/dist/nifi/nifi-fds/nifi-fds-0.2.0/nifi-fds-0.2.0-source-release.zip.sha512";>sha512</a>
)</li>
+ </ul>
+ </li>
+ <li><a
href="https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.2.0";>Release
Notes</a></li>
+ </ul>
+ </li>
+ <li>
+ 0.1.0
+ <ul>
+ <li>
+ Sources
+ <ul>
+ <li><a
href="https://archive.apache.org/dist/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip";>nifi-fds-0.1.0-source-release.zip</a>
(
+ <a
href="https://archive.apache.org/dist/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.asc";>asc</a>,
+ <a
href="https://archive.apache.org/dist/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha256";>sha256</a>,
+ <a
href="https://archive.apache.org/dist/nifi/nifi-fds/nifi-fds-0.1.0/nifi-fds-0.1.0-source-release.zip.sha512";>sha512</a>
)</li>
+ </ul>
+ </li>
+ <li><a
href="https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.1.0";>Release
Notes</a></li>
+ </ul>
</li>
</ul>
</p>
Modified: nifi/site/trunk/mailing_lists.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/mailing_lists.html?rev=1897878&r1=1897877&r2=1897878&view=diff
==============================================================================
--- nifi/site/trunk/mailing_lists.html (original)
+++ nifi/site/trunk/mailing_lists.html Tue Feb 8 19:24:27 2022
@@ -227,7 +227,7 @@
<ul>
<li>
Apache NiFi Slack Workspace: <a
href="https://apachenifi.slack.com/";>https://apachenifi.slack.com/</a> <br />
- New users can join the workspace using the following <a
href="https://s.apache.org/nifi-community-slack";>invite link</a>.
+ New users can join the workspace using the following <a
href="https://join.slack.com/t/apachenifi/shared_invite/zt-11njbtkdx-ZRU8FKYSWoEHRJetidy0zA";>invite
link</a>.
</li>
<li>
IRC: #nifi on <a
href="http://webchat.freenode.net/?channels=#nifi";>irc.freenode.net</a>
Modified: nifi/site/trunk/registry-security.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/registry-security.html?rev=1897878&r1=1897877&r2=1897878&view=diff
==============================================================================
--- nifi/site/trunk/registry-security.html (original)
+++ nifi/site/trunk/registry-security.html Tue Feb 8 19:24:27 2022
@@ -140,8 +140,8 @@
<h3>Reporting Methods</h3>
<p>NiFi Registry receives vulnerability reports through the Apache
NiFi team via the following means:</p>
<ul>
- <li>Send an email to <a
href="mailto:[email protected]";>[email protected]</a>. This is a
private list monitored by the <a href="people.html">PMC</a>. For sensitive
- disclosures, the GPG key fingerprint is <strong>1230 3BB8 1F22
E11C 8725 926A AFF2 B368 23B9 44E9</strong>.
+ <li>NiFi Security Mailing List: <a
href="mailto:[email protected]";>[email protected]</a>.
+ Members of the <a href="people.html">Project Management
Committee</a> monitor this private mailing list and respond to disclosures.
</li>
</ul>
<p>Thank you for helping keep Apache NiFi Registry and our users
safe!</p>
Modified: nifi/site/trunk/security.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/security.html?rev=1897878&r1=1897877&r2=1897878&view=diff
==============================================================================
--- nifi/site/trunk/security.html (original)
+++ nifi/site/trunk/security.html Tue Feb 8 19:24:27 2022
@@ -147,8 +147,9 @@
<h3>Reporting Methods</h3>
<p>NiFi accepts reports in multiple ways:</p>
<ul>
- <li>Send an email to <a
href="mailto:[email protected]";>[email protected]</a>. This is a
private list monitored by the <a href="people.html">PMC</a>. For sensitive
- disclosures, the GPG key fingerprint is <strong>1230 3BB8 1F22
E11C 8725 926A AFF2 B368 23B9 44E9</strong>.
+ <li>NiFi Security Mailing List: <a
href="mailto:[email protected]";>[email protected]</a>.
+ Members of the <a href="people.html">Project Management
Committee</a> monitor this private mailing list and respond to disclosures.
+ </li>
</li>
<li>NiFi has a <a href="https://hackerone.com/apachenifi";
target="_blank">HackerOne</a> project page. HackerOne provides a triaged
process for researchers and organizations to
collaboratively report and resolve security vulnerabilities.
