<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/cfv/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/cfv/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 12 Dec 2017 10:52:19 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/cfv/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>#1 checksum file update functionality</title><link>https://sourceforge.net/p/cfv/feature-requests/1/?limit=25#c38a</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I'm aware that this is 15-year necroposting, but I'd like to add a clarifying point.&lt;/p&gt;
&lt;p&gt;It seems to me that there are two things one might mean when one says "to update checksum files".&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;When the files themselves have changed. This is similar to what's discussed here in the OP. The only way I see this working is if the timestamp (and filesize) information also be kept (akin to how rsync performs its 'quick' verification) - simply re-checking and replacing the checksums seems to be inviting disaster (defeating the entire point of an integrity tool, potentially overwriting valid checksums when your files merely got corrupted), and specifying individual files manually could get cumbersome, fast.&lt;/li&gt;
&lt;li&gt;When files are simply added/removed. This matches my desired use case, where I have a media library where even within one subfolder files are added/removed (mostly added) on a semi-regular basis. My current workflow is to first verify the existing files, then backup the previous checksum file, then generate a fresh one, but that wastes a lot of time. I would expect one flag which simply assumes that old files are fine (unless they've been removed, and removes their checksums) and adds new files to the checksum lists, with an additional flag to enforce the verification of the files which existed before.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Have I overlooked one of the supported checksum file formats already supporting timestamps/filesizes? (Except for .torrent, since I'd prefer plaintext)&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Adam</dc:creator><pubDate>Tue, 12 Dec 2017 10:52:19 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netdd4e26f45d19bf7a61a4736604193489f46b14c0</guid></item><item><title>dry run option</title><link>https://sourceforge.net/p/cfv/feature-requests/14/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hello, first of all thanks for the awesome project. I mainly use it for verifying files, but sometimes use it for creating checksum files, too.&lt;/p&gt;
&lt;p&gt;One option i am missing is the dry run option. With this, we can have cfv show the result of an action without actually performing that action. This is great for testing different options when using the create mode. It can be implemented with a switch like --dry-run.&lt;/p&gt;
&lt;p&gt;Thanks and keep up the great work.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">temp_user</dc:creator><pubDate>Fri, 27 May 2011 04:41:57 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0e84d1120b4981b2140b68b450a255d54e6bdb26</guid></item><item><title>please add sha256 hash</title><link>https://sourceforge.net/p/cfv/feature-requests/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I would like to use sha256 hashing for verification,&lt;br /&gt;
and I prefer to keep using your excellent program.&lt;br /&gt;
As you likely know, any verification that must be reliable over the long term must be strong enough to &lt;br /&gt;
withstand future threats, not just current ones. &lt;br /&gt;
Moore's law is the best-case, not the worst-case scenario.&lt;br /&gt;
Since sha-1 has been shown to have some weaknesses, government use of sha-1 has been restricted somewhat.&lt;br /&gt;
Debian now has sha-256 hashes on all deb packages&lt;br /&gt;
(see apt-cache search --full cfv)&lt;br /&gt;
Thanks again.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Charles Evans</dc:creator><pubDate>Mon, 03 May 2010 09:47:51 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net238ed894606e71e790d8d57944ed8cf18e0e22eb</guid></item><item><title>please add an option to exclude files or dirs</title><link>https://sourceforge.net/p/cfv/feature-requests/12/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Please add something like --exclude=&lt;br /&gt;
as rsync and tar have. &lt;br /&gt;
Thanks!&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Charles Evans</dc:creator><pubDate>Mon, 03 May 2010 09:31:49 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net02f474878f08e6256672499225aa4739b336c760</guid></item><item><title>add option to not follow any symlinks but sum their readlink</title><link>https://sourceforge.net/p/cfv/feature-requests/11/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I often have links to partition image files of many gigabytes, &lt;br /&gt;
and many links to each of my distro's DVDnn.iso files, so&lt;br /&gt;
scanning a dir may take hours longer as each of 10  iso's is summed 10+ times. 400GB+ total extra.&lt;br /&gt;
An option to not follow any symlinks would fix this.&lt;br /&gt;
Another option to not follow any symlinks except those given on the command line &lt;br /&gt;
would be even better, but half the time I need these to be not followed either.&lt;br /&gt;
Symlinks not followed should have their readlink value summed instead&lt;br /&gt;
so the sig will change if the symlink is changed or replaced.&lt;br /&gt;
Thanks for a great program!&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Charles Evans</dc:creator><pubDate>Mon, 03 May 2010 08:53:08 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7fc2129152bb3076ad3100ff2f0013fce2e2d8bd</guid></item><item><title>add comment for .torrent file creation</title><link>https://sourceforge.net/p/cfv/feature-requests/10/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be great, if we could add a comment to the torrent file.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sat, 13 Jun 2009 06:55:41 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net507c66fcfb38af1469407f9edd41e38293913603</guid></item><item><title>cfv should be able to compare against filename-embedded CRCs</title><link>https://sourceforge.net/p/cfv/feature-requests/9/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;For example, certain files frequently contain a CRC32 checksum embedded in the filename. At the moment I use a script to extract these checksums from the filename and put them in a .sfv file. I then run cfv.&lt;/p&gt;
&lt;p&gt;I propose that there be an option to calculate the checksum of a file and compare that to substrings in the filename. If the checksum (case-insensitively) matches a substring of the filename, the file is marked OK.&lt;/p&gt;&lt;/div&gt;</description><pubDate>Wed, 30 Jul 2008 11:29:48 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net43ea6659520087625bc1b871296ba4d2605bcc8d</guid></item><item><title>Compute multiple checksums in parallel</title><link>https://sourceforge.net/p/cfv/feature-requests/8/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;CFV can compute several different checksum (i.e. MD5 and SFV) at once, however the process is very inefficient: the checksums are simply computed one after another, meaning that each file is read multiple times. A better approach would be to comupte checksums in parallel, reading each file just once.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wandermind</dc:creator><pubDate>Mon, 11 Feb 2008 03:33:19 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net9e6865d63e34506b8de617c5a09a9f97f2da01f1</guid></item><item><title>adding the private flag for .torrent files</title><link>https://sourceforge.net/p/cfv/feature-requests/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be great if .torrent-files could optionally be flagged as being private, so that Bittorrent-clients do always use the Bittorrent-Tracker and don't use the Peer Exchange Extension (PEX) or the Distributed Hash Table (DHT).&lt;/p&gt;
&lt;p&gt;Right now, &lt;a href="http://mktorrent.sourceforge.net/"&gt;http://mktorrent.sourceforge.net/&lt;/a&gt; seems to be the only cli application to create .torrents with the private flag being set.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anders Henke</dc:creator><pubDate>Wed, 09 Jan 2008 14:45:26 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0e498d3324d36aeeda4f650747eef75da04c18c3</guid></item><item><title>adding SHA1 hash handling</title><link>https://sourceforge.net/p/cfv/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;to file, format like MD5SUM.lst, but having SHA1 hash &lt;br /&gt;
instead of MD5.&lt;br /&gt;
Thank you.&lt;br /&gt;
P.S. or I can develop and send you patch? ;)&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Denis</dc:creator><pubDate>Wed, 01 Dec 2004 13:37:50 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net04aee6f987bb8224dd4fe2235b7ed188c10b7564</guid></item></channel></rss>