Hello David,
the "simplest" way to compromise Clipperz is to change the code of its
application, that is the code your browser is downloading in order to
give you access to your data.
At the moment there are no perfect solutions to avoid this problem
altogether, but there are some simple steps that could alert you if
something wrong is going on. If you look into the forum for 'checksum'
you will find some hints about a script we have posted that could
check that the Clipperz application has not been tampered before
redirecting you to the real site.
To have a preview of what it looks like, take a look at my
del.icio.us
bookmark at
-
http://del.icio.us/gcsolaroli/clipperz
DISCLAIMER: the script used by that link is hosted on the same server
where the main Clipperz application is running, so it would be quite
trivial for an attacker to compromise both the script and the
application in case of an intrusion. But if you can host the same
script on another random host, using it as a gateway to Clipperz can
greatly improve your security.
Other than this, we have been included in a project done by some
Stanford/Berkley students on security vulnerabilities of javascript
bookmarklets and they have found a problem on how we used to handle
the direct login configurations collected through the bookmarklet. But
this problem has long been fixed.
We are not aware of other security issues with regard to our service.
Best regards,
Giulio Cesare