search

viper-framework / viper

Binary analysis and management framework
Other
1.54k stars 351 forks source link

Wrong project database used when starting viper-cli with -p #661

Closed kovacsbalu closed 6 years ago

kovacsbalu commented 6 years ago

When you create a new project with viper-cli -p foo Viper create folder within projects and put stored files and init database, but file store data inserted to default viper.db

./viper-cli -p aaa

aaa viper > about
+----------------+-------------------------------------------------+
| About          |                                                 |
+----------------+-------------------------------------------------+
| Viper Version  | 2.0-dev                                         |
| Python Version | 2.7.6                                           |
| Homepage       | https://viper.li                                |
| Issue Tracker  | https://github.com/viper-framework/viper/issues |
+----------------+-------------------------------------------------+
+--------------------+-----------------------------------------+
| Configuration      |                                         |
+--------------------+-----------------------------------------+
| Configuration File | /home/user/.viper/viper.conf         |
| Active Project     | aaa                                     |
| Storage Path       | /home/user/.viper/projects/aaa       |
| Database Path      | sqlite:////home/user/.viper/viper.db |
+--------------------+-----------------------------------------+
kovacsbalu commented 6 years ago

and also find...and every base command within commands.py use .viper/viper.db

frennkie commented 6 years ago

I ran into the same issue just today .. good catch.. :-)