Open aureliencarle opened 2 years ago
@GregoireUhlrich As plug-in is left as a cryptext door for user, it can be clever to read the plug-in file from $HOME/.cryptext directory. HOME |-- pass |-- plug-in
Let some generic plugin in plugin directory of the program an read both directory..
@aureliencarle indeed, the access using a relative path at run-time is anyway not reliable. The plugin code can be located in the cryptext directory and the input location could be provided by the user (either in the command parameters or as an input()
command)
.cryptext structure is now done, see #35
I need to start right now a "plug-in" to convert browser pass word to crpytext object ... Maybe this plug-in will not be conserved but I need it right now for me ;)