LibSecRm - Secure Removal Library / The LSR Blog: Recent posts

The first version of LibSecRm, 0.1, was created (but not published on SF at that point yet) on 2007-07-08, so July the 8th can be considered LibSecRm's "birthday".
Rare releases, but the project is still active.

The project ticket tools (Defects and Tickets) have been recreated, hopefully this time for good.

LibSecRm version 3.3 has just been released!
Important changes:

• Fixed compile errors after name randomisation.
• Added support for fallocate64().
• Checking for more compile warnings.
• Portability updates - LibSecRm now compiles on Solaris/SunOS.
• Added support for systems with a less advanced /proc filesystem.
• Code quality updates.
• Updates in the build system.
• Updates in unit tests and new tests (current coverage: 46.2%).
• Documentation updates.

The project ticket tools (Defects and Tickets) have disappeared again.
I've reported this to SF.

The first version of LibSecRm (not published by then), was created on 2007-07-08, so July the 8th can be considered LibSecRm's "birthday".
Not many releases recently, but there is work being done off-line.

According to the ChangeLog file, the very first version of LibSecRm, 0.1, was created on 2007-07-08.
It wasn't on SourceForge from the beginning , but nevertheless July the 8th can be considered LibSecRm's "birthday".

The problem with disappearing "Tickets"/"Defects" seems to be resolved now.

The documentation in the TeXinfo format (which normally resides only inside the packages) has been converted to HTML and provided on the project website at https://libsecrm.sourceforge.io/docs/ for convenience. This documentation should provide more information to current and potential users.
Remember that the most up-to-date documentation is always in the software package.

There seems to be some temporary problem with project tickets (Defects and Tickets): they disappear after a few days after being created.
I've reported this to SF.

Significant portability updates. LibSecRm now compiles on FreeBSD and macOS (as provided by Travis CI): https://app.travis-ci.com/github/bogdro/libsecrm.
Allow setting the number of iterations using an environment variable.
Improvements in banning.
Improvements in the build system.
Improvements in code quality.
Significant improvements in the documentation.
New unit tests.

LibSecRm has been checked by Codacy and got the "A" grade. Current status:

LibSecRm has been uploaded to a test repository on GitHub, has passed a build on their system and a code security check (the only warning is about a temporary file used by configure).

According to the ChangeLog file, the very first version of LibSecRm, 0.1, was created on 2007-07-08.
It wasn't on SourceForge from the beginning (my projects need to have at least a few versions and a forseeable future to be promoted to SF), but nevertheless July the 8th is LibSecRm's "birthday".
Helping users keep their privacy for 15 years!

As a result of SF's encouragement to using icons, I've decided to do some experiments with the Inkscape program.
I chose Scalable Vector Graphics (SVG) because I wanted the icon to be scalable to any size without losing quality and the only way to achieve that is with vector graphics.
The icon may be "tuned" or even fully changed later, but for now you can enjoy the current looks on the project page on SF and on the LibSecRm's homepage at https://libsecrm.sourceforge.io/ (both in the content and as the site icon). These icons are in the PNG format (another open standard), because this is what SF allows here, but the source is still SVG.

The LibSecRm's website (https://libsecrm.sourceforge.io/) got a content listing at the top. The order of the sections has also been changed to hopefully provide information in the most important order (which is subjective for the reader).

Encouraged by SF, I've decided to launch blogs for my software hosted here (IMYplay, LibHideIP, LibNetBlock, LibSecRm, JYMAG and WipeFreeSpace).
The blog will be a place where I will announce noteworthy changes to LibSecRm or its website, and new releases.
Remeber that the first place that gets notifed of a new release is ... the release page on SF (called "Files"), so be sure to watch that one as a first source of information on new releases. The page also has a data feed!