[guardian-dev] Ripple app

Hans-Christoph Steiner hans at guardianproject.info
Mon Dec 12 07:41:10 EST 2016

Those are also very useful things for a panic setup.  The other key part
of the design of Panic Kit is that triggers are separate from responses.
 So things like deleting, sending messages, backing up data, etc. should
be in a "responder" app.  Then any trigger app can include that as one
of the possible responses, including your Ripple fork.

Our InThe Clear could provide some examples for various deletion tasks:

Another thing to consider is the whole SQLCipher/IOCipher/CacheWord
model of secure, app-local data storage.  CacheWord manages the key to
SQLCipher/IOCipher, and the user unlocks that key with their password.
If the CacheWord key file is deleted, the user no longer has a way to
unlock SQLCipher/IOCipher: the user's password unlocks the key only, not
the data.  So then you can just backup the tiny cacheword key file (<
1kb), then in a panic delete just that.  Then once things are safe, just
restore that tiny file.


> ok, as you suggest i'm gonna do a hard fork of the project and start my own
> app.
> I'm gonna do something more complex where Ripple was only one of the
> possible actions.
> I would like to allow:
> - Delete a user configurable folder list
> - Use a tool like secure-delete for delete sensible data
> - Backup data to a secure server before delete
> - Send an alert message (via sms , publish to social networks,.......)
> - Send ripple to others apps
> - .........i'm thinking :)
> A feature request will be taken in consideration :)
> 2016-12-12 13:13 GMT+01:00 Hans-Christoph Steiner <hans at guardianproject.info
>> :
>> I think those are great ideas for a panic button app.  I'm not sure that
>> Ripple is the app to have those.  One of the core ideas of Ripple, as
>> well as all Panic Kit work, is that the panic trigger apps can be made
>> super simple with as little config or options as possible so that they
>> are dead simple to understand and use.  Setting up panic buttons is
>> already stressful enough as it is, so the apps that work in that
>> ecosystem need to strive to avoid that stress.  This design is bourne
>> out of experience with our InTheClear app and Amnesty Intl's Panic Button.
>> That said, the whole panic button idea needs more people thinking about
>> UX and making working designs so that we can find out what actually
>> works for people.  So I encourage you to fork Ripple and publish your
>> own panic button app.  The code is quite simple as it is, so I don't
>> think there is much maintenance work to be shared.
>> Also, FYI, multiple panic trigger apps can be installed and active at
>> the same time.
>> .hc
>> arrase:
>>> I made a pull request with two features:
>>> - An option for disable countdown
>>> - An option for run PanicActivity  when user logs in after a configurable
>>> number of unsuccessful password attempts
>>> Thank can be usseful if some forces you to unlock your device, then you
>> can
>>> set a bad password a number of time and when finally you login you have a
>>> chance for quickly lauch a Ripple action.
>>> But in other hand there is a chance than your opponet holds the device
>> and
>>> ask you for a the pin, so i'm thinking in add an option for raise Ripple
>>> acion withouth swipe confirmation after a number unsuccessful password
>>> attempts.
>>> 2016-12-11 19:11 GMT+01:00 arrase <arrase at gmail.com>:
>>>> Hi,
>>>> I would like to add some features to Ripple App:
>>>> - fire ripple from a persistant notification
>>>> - an option for disable the countdown
>>>> - fire ripple after user unlocks the device if a user predefined
>> sequence
>>>> of hardware buttons was clicked
>>>> What do you think about?
>> --
>> PGP fingerprint: EE66 20C7 136B 0D2C 456C  0A4D E9E2 8DEA 00AA 5556
>> https://pgp.mit.edu/pks/lookup?op=vindex&search=0xE9E28DEA00AA5556

PGP fingerprint: EE66 20C7 136B 0D2C 456C  0A4D E9E2 8DEA 00AA 5556

More information about the guardian-dev mailing list