Updating FISSURE Challenge section in README

ainfosec · Jan 2, 2024 · 61e04e8 · 61e04e8
1 parent b5614c5
commit 61e04e8
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 6 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,6 +1,14 @@
 # Change Log
 All notable changes to this project will be documented in this file.
 
+## 2024-01-02
+
+Updating FISSURE Challenge section in README
+
+### Changed
+
+- Moved and edited FISSURE Challenge section in README
+
 ## 2023-12-22
 
 First attempt at Raspberry Pi OS (bookworm) install

diff --git a/README.md b/README.md
@@ -14,12 +14,6 @@ The friendly Python codebase and user interface allows beginners to quickly lear
 <img src="/docs/Icons/README/rf_re.png" width="400" height="400">
 </p>
 
-## :triangular_flag_on_post::triangular_flag_on_post::triangular_flag_on_post: 2023 FISSURE Challenge :triangular_flag_on_post::triangular_flag_on_post::triangular_flag_on_post:
-
-The first annual [FISSURE Challenge](https://fissure.ainfosec.com/) will be held online December 20-31, 2023. The event is a free CTFd capture-the-flag competition with the goal of highlighting a new subset of features and tools added to FISSURE each year. No SDRs will be required for any of the challenges this first go around. The challenges will be archived and made available after the event. Monitor the event on Discord and Twitter. Register and view details at:
-
-- https://fissure.ainfosec.com/
-
 ## Documentation
 
 <p align='center'>
@@ -301,6 +295,10 @@ FISSURE comes with several helpful guides to become familiar with different tech
 - [ ] Support new GNU Radio releases
 - [ ] Update the project idea list every year
 
+## FISSURE Challenge
+
+The annual "FISSURE Challenge" capture-the-flag contest to showcase new additions to FISSURE is held in December each year. Past challenges are archived and can be solved all year round! Gain hands-on experience and view solutions at: [FISSURE Challenge](https://fissure.ainfosec.com/).
+
 ## Contributing
 
 Suggestions for improving FISSURE are strongly encouraged. Leave a comment in the [Discussions](https://github.com/ainfosec/FISSURE/discussions) page or in the Discord Server if you have any thoughts regarding the following: