Skip to content

Commit d75a191

Browse files
authored
Merge pull request #161 from carloslack/unreleased-changelog
docs: Update CHANGELOG
2 parents e901d15 + 8c82cc6 commit d75a191

File tree

3 files changed

+19
-15
lines changed

3 files changed

+19
-15
lines changed

CHANGELOG.md

+16-6
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,22 @@ All notable changes to KoviD will be documented in this file.
55
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/).
66

77
## Unreleased
8-
- `/proc` UI re-worked with `match_table`
9-
- `/proc` UI visibility handled by `statx`
10-
- Key is required for back-door connections
11-
- Add how-to-write-test doc
12-
- Add KoviD initial regression tests: back-doors, hide processes, module and more.
13-
- Add `cmake` build system for tests framework
8+
### Fixed
9+
- test: False positive for `BUG: unable to handle page fault` related to `llvm.lit` test runner
10+
11+
### Changed
12+
- protect, with encryption, memory stored back-door Key
13+
- proc UI re-designed
14+
- black-list proc UI from directory stats
15+
16+
### Added
17+
- Feature: tamper stat's counter (`Links:`) for hidden hard-links
18+
- Feature: basic encryption
19+
- Tools: x86-64 lkm loader under `inject/`
20+
- Tests: `ftrace`, back-doors, `proc`, `Kaudit`
21+
- Tests: KoviD initial regression tests: back-doors, hide processes, module
22+
- Tests:`cmake` build system for tests framework
23+
- Tests: Native tests
1424

1525
## 2.1.1 - Oct 19 2024
1626
### Fixed

docs/ReleaseNotes.md

-6
This file was deleted.

docs/ReleaseProcess.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@ This document outlines the steps required to prepare, validate, and publish a ne
1414
1. Determine the next release version according to the versioning policy.
1515
2. Update the version number.
1616

17-
### 2. Update Release Notes
18-
1. Open `docs/ReleaseNotes.md`.
17+
### 2. Update Changelog
18+
1. Open `CHANGELOG.md`.
1919
2. Add a summary of changes, including new features, bug fixes, and any known issues since the last release.
2020
3. Ensure notes are clear, accurate, and helpful.
2121

@@ -85,7 +85,7 @@ Replace vX.Y.Z with your new version.
8585

8686
1. Create a new release on GitHub.
8787
2. Use the newly created tag.
88-
3. Include ReleaseNotes.md content in the release description.
88+
3. Include CHANGELOG.md content in the release description.
8989
4. Optionally attach binary.
9090

9191
### 8. Announcement (Optional)

0 commit comments

Comments
 (0)