On 08/03/2017 04:08 AM, John Horne wrote: > On Thu, 2017-08-03 at 11:37 +0100, Dogsbody wrote: >>> >>> From a coding point of view it would be nice to move to github. >>> >> >> I would love to see this project move to GitHub and I consider the >> issues functionally way more useful than a mailing list as you can >> receive emails if you wish but being able to have a threaded view with >> links actual code and dependencies is wonderful. >> > The 'issues' part would replace the sourceforge (SF) 'tickets' system. So > reporting bugs etc should not be a problem.
You could also look at Fedora's pagure.io: https://pagure.io/ > My concern though is that currently RKH allows users to update the data files > via SF (using 'rkhunter --update'). Moving to github would basically remove > that functionality. Users could manually update the files by downloading them > from github, but I suspect that would not go down too well! An alternative is > to remove that functionality from RKH, and only provide static data at each > release. Again, not ideal, however the data files themselves do rarely change. How about making those updates a git repo and having the client 'git pull' the https url ? You could even sign commits and have it check them for added security, and folks could even sync local copies of them if desired. kevin
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Rkhunter-users mailing list Rkhunter-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkhunter-users
