Armory does launch crazy sh command

[yhaenggi]

trafficstars

So when i start Armory, it starts the following command in the background:

 2962 pts/17   S+     0:00 /bin/sh -c find /home/k1773r -type f -name "mimeTypes.rdf"
 2963 pts/17   D+     0:00 find /home/k1773r -type f -name mimeTypes.rdf

armory continues to work if you kill it. if you kill it, no output is seen on the terminal (if armory is started in a terminal) and i also found no infos related to it at all.

what is this? my $HOME is huge and this find takes ages to complete and only wastes alot of IO.

[goatpig]

Looks for a Firefox file to register bitcoin: URIs with it. You can entirely turn that off by getting rid of the registerURI calls in ArmoryQt.py startup. procedure.

[yhaenggi]

after setting DNAA_DefaultApp to False, it asked me if i want to register bitcoin URI with armory, if you check no and check remember, it still executes given command. IMHO it should only check for that file if you enabled it. also you could just search in $HOME/.mozilla/firefox/ which would reduce the time for finding it alot. or even better (if available) use locate (mlocate).

[goblin]

This is extremely wrong! For each file found, it looks like Armory will silently append several lines to that file! What if I had a backup of something very important called 'mimeTypes.rdf' in my home directory? Armory would silently corrupt that file by appending its stuff! This is totally unacceptable.

I actually have several .mozilla backups in my home dir, I really don't want Armory to break those! It has no right to write to those files.

Also if something else was writing to that file there is a race condition in the appending code that could corrupt the file way more than just by appending stuff that can later be removed.

Just what other crazy stuff does Armory attempt to do with my filesystem? :-S

[yhaenggi]

So, whats the status of this? accept as broken?

[achow101]

Armory is no longer being developed in this repo. Development now happens in https://github.com/goatpig/BitcoinArmory. If you still experience the issue with the latest version of Armory (0.96), then make an issue in the new repo.