Request for personal-files access for boxwallet

store-requests
52

Yes thank-you that makes sense.

+1 from me for boxwallet for use-of and auto-connect of personal-files instances as follows (note write access implies read so there is no need to include read as well):

plugs:
  dot-digibye:
    interface: personal-files
    write:
      - $HOME/.digibye
  dot-divi:
    interface: personal-files
    write:
      - $HOME/.divi
  dot-feathercoin:
    interface: personal-files
    write:
      - $HOME/.feathercoin
  dot-devault:
    interface: personal-files
    write:
      - $HOME/.devault
  dot-groestlcoin:
    interface: personal-files
    write:
      - $HOME/.groestlcoin
  dot-phore:
    interface: personal-files
    write:
      - $HOME/.phore
  dot-pivx:
    interface: personal-files
    write:
      - $HOME/.pivx
  dot-reddcoin:
    interface: personal-files
    write:
      - $HOME/.reddcoin
  dot-scala:
    interface: personal-files
    write:
      - $HOME/.scala
  dot-trezarcoin:
    interface: personal-files
    write:
      - $HOME/.trezarcoin
  dot-vertcoin:
    interface: personal-files
    write:
      - $HOME/.vertcoin

NOTE: originally I said above to auto-connect these but @ijohnson correctly reminded me that unless a snap is the clear owner of a given path it then the usual precedent is to give the user a chance to opt-in for these sorts of accesses and so only allow use of, but not auto-connect of a given personal-files instance.

Since boxwallet is not the clear owner of these paths, these should be manually connected then, so my vote above is just for use of, but NOT auto-connect of these personal-files instances.

1 Like