search

nowsecure / fsmon

monitor filesystem on iOS / OS X / Android / FirefoxOS / Linux
https://www.nowsecure.com
MIT License
881 stars 151 forks source link

the fsmon work in android problem #36

Closed joeycold closed 5 years ago

joeycold commented 5 years ago

both in arm or x86, the android version seems like not work.it just output this info: ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0

the make command i use: make android NDK_ARCH=x86 ANDROID_API=21 make android NDK_ARCH=arm ANDROID_API=21

trufae commented 5 years ago

This seems like a regression. Which version if androird are you using to test this?

How do you run fsmon to get those messages?

Also, it is recommended to quote the code snippets to ease reading the issue

Thanks

On 19 Dec 2018, at 10:21, kuroba notifications@github.com wrote:

both in arm or x86, the android version seems like not work.it just output this info: ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0 ?[33mFSE_CONTENT_MODIFIED?[0m 0 "?[35m?[0m" 0

the make command i use: make android NDK_ARCH=x86 ANDROID_API=21 make android NDK_ARCH=arm ANDROID_API=21

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

joeycold commented 5 years ago

thank you for reply. I test the x86 binary in Android x86 emulator with 5.0.and anthor arm version in my nexus6 with Android 6.0.

also I test the x86 binary on releases page with x86 emulator 5.0,it also work incorrect: image image the output is very very fast.

the arm binary seems better,look it: https://pastebin.com/h5GphrEJ at least I can see some file name.

finally I try to build an arm binary with android 6.0(NDK 27),but seems like the new NDK 27 Directory Structure is different to old version,so it make faild with error.

trufae commented 5 years ago

ive added the -n flag to not spit out ansi escape codes. that wont solve the issue, but at least will make the output readable on windows consoles

trufae commented 5 years ago

You may specify the root directory and use the -n flag (from last release) that may work fine for you. please confirm and i'll close the issue

joeycold commented 5 years ago

sorry for late reply. I test the last release fsmon-and-x86 on emulator(android 5.0 x86).it dosen't work. image and last release fsmon-and-arm in android 6.0 image I don't understand "You may specify the root directory"?

trufae commented 5 years ago

Uhm ive tested it on 6,7,8,9 and works as expected if running as root and passing root means to execute it like this: “fsmon /“

On 16 Feb 2019, at 12:26, kuroba notifications@github.com wrote:

sorry for late reply. I test the last release fsmon-and-x86 on emulator(android 5.0 x86).it dosen't work.

and last release fsmon-and-arm in android 6.0

I don't understand "You may specify the root directory"?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

trufae commented 5 years ago

To solve the support fort android5 you may need to build fsmon with an older NDK, this "register_atfork" symbol is not coming from fsmon, probably a bionic version change