App data storage

[osysltd]

Dear Ikarus,

First of all thank you for such high quality development!

A quick question\feature request:
Is it feasible to store the app data in the /data partition (or add an option to store the info there) as this is the only place which is being encrypted on the encryption-enabled smartphone. The aim is to be on the safe side having custom dictionary keys and dumps and prevent unauthorized access to the information.

Thank you.

[ikarus23]

Hi osys,
this seams like a reasonable option. I put the data on the external memory so everybody can
easily backup or modify them and they do not get lost if the app gets uninstalled. However, if
you store real secret keys then of course it would be best to store them in the /data partition.
I will add an option that allows you to switch between internal and external memory. But as
always, I'm not sure when I will have the spare time to implement it. ;)

[ikarus23]

I implemented this feature. You can try it using this MCT testing version. There will be a release containing this feature once I had a look into some other construction sites of MCT.

[bxl0608]

Thanks very much! I will install it.

…

-------- 原始邮件 -------- 发件人：ikarus <[email protected]> 时间：周日 3月5日 22:55 收件人：ikarus23/MifareClassicTool <[email protected]> 抄送：Subscribed <[email protected]> 主题：Re: [ikarus23/MifareClassicTool] App data storage (#103)

I implemented this feature. You can try it using this MCT testing version. There will be a release containing this feature once I had a look into some other construction sites of MCT. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread. {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/ikarus23/MifareClassicTool","title":"ikarus23/MifareClassicTool","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in ***@***.*** in #103: I implemented this feature. You can try it using [this MCT testing version](http:https://tests.icaria.de/MifareClassicTool-2.1.0-testing.apk). There will be a release containing this feature once I had a look into some other construction sites of MCT."}],"action":{"name":"View Issue","url":"#103 (comment)"}}}

[osysltd]

Unfortunately I cannot install on Android 5.1.1.
*** Previous version from GooglePlay uninstalled

[ikarus23]

Yes, you cannot have both versions installed at the same time. You have to uninstall MCT before you install this version. Your dumps and key files will survive this. However, if you use the "save on internal storage" option from this version, all data in the internal storage will be gone once you uninstall it again. Have a look at the information on the new option, which are available within the app.

[ikarus23]

Maybe I will add an import/export function for files from and to the internal storage. But I'm not sure if that's worth the effort. If the keys in your key file are that secret, you probably should not carry them on your phone all the time...

[osysltd]

Previous version from GooglePlay was uninstalled prior to the installation.

[ikarus23]

Maybe I should have read you comment more carefully... Sorry.

Well, I rebuild the app using the old app signing method. Now it should work. I substituted the apk in the link above. Just download it again.

[osysltd]

Dear Ikarus,
Thank you for your reply. I've deleted any mct from device and installed the latest version. In the settings set up the option to use the internal storage, however can see that the storage folder is appearing in two places: /storage/emulated/0/MifareClassicTool and also /data/data/de.syss/MifareClassicTool. Is that expected? Default key files are equal in these places. Ive also deleted these folders but they reappeared both of them after relaunching the app. Btw fyi the only encrypted folder is /data/data/de.syss... the other one can be viewed from custom recovery for example.

[ikarus23]

Hi @osysltd, yes this is expected. MCT creates the basic structure at both places. I know that only data at /data/data/... is protected. As long as you use the new option new key and dump files will be stored at /data/data. You can switch when ever you want.

[osysltd]

Cool! thank you very much for the efforts, now mct users can be on the safe side.

[ikarus23]

You are welcome. Thank you for testing!