Andrew,

As a commiter, I have to be careful that my opinion may be construed
as the viewpoint of the DSpace developers. So I will clarify that this
is only my opinion, not the groups.

I've never been impressed with the reasoning behind this addition to
DSpace, it mistakes bitstream security and file corruption as
something that should be tracked by the DSpace application. We
encountered problems with the checksum checker getting bogged down due
to some issue in the code/database.  I was never able to get it
restarted and continued to waste time on it until our IT Systems Admin
showed me the light...

A real file integrity system should be implemented outside of the
application by an experienced system administrator vested in
maintaining the security and integrity of the system, not in the
application by a webapplication developer.  I do value and respect the
team that developed this addon to DSpace, but disagree with the
approach and the complexity of the code.  Instead I would recommend
running something more professional like the following on ones
assetstore.

http://www.sentry-go.com
http://www.cs.tut.fi/~rammer/aide.html
http://www.tripwire.com
http://www.solidcore.com/

Cheers,
Mark


On Fri, Apr 17, 2009 at 12:10 AM, Andrew Marlow
<[email protected]> wrote:
> Hello DSpacers,
>
> I came across the checksum checker recently and I don't understand why it is
> useful. Here is what I found on the WIKI:-
> ---
> DSpace now comes with a Checksum Checker script ([dspace]/bin/checker) which
> can be scheduled to verify the checksum of every item within DSpace. Since
> DSpace calculates and records the checksum of every file submitted to it,
> this script is able to determine whether or not a file has been changed
> (either manually or by some sort of corruption or virus).
> ---
> So why would an item be corrupt? Or altered manually? I know that any
> filesystem object can get problems when the filesystem goes wobbly, that's
> why we have backups. But surely the normal operating system monitoring
> utilities will tell us when a filesystem needs repair? Can someone explain
> please?
> --
> Regards,
>
> Andrew M.
> http://www.andrewpetermarlow.co.uk
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>



-- 
Mark R. Diggory
http://purl.org/net/mdiggory/homepage - Bio

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to