Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to add an sftp directory correctly to permissions? #708

Open
thepragmaticmero opened this issue Sep 1, 2024 · 4 comments
Open

How to add an sftp directory correctly to permissions? #708

thepragmaticmero opened this issue Sep 1, 2024 · 4 comments

Comments

@thepragmaticmero
Copy link

I want to add permission the following folder correctly.
image
/run/user/1000/gvfs/sftp:host=192.168.18.21/home/ideapadhdd
I'm worried about the little exclamation mark at the side. It appears instantly after typing a colon :.
Should I replace it with /run/user/1000/gvfs/? It's stops complaining with that file path.

My obsidian vault needs access to that specific folder. The Obsidian.appimage didn't complain about access to sftp(because the lack of sandboxing).

@rusty-snake
Copy link

I'm worried about the little exclamation mark at the side.

Hover them to show a tooltip.

Also you can easily check if it works as expected by using flatpak run --command=sh <app-id>.

@thepragmaticmero
Copy link
Author

$ flatpak run --command=bash md.obsidian.Obsidian
F: Unexpected filesystem suffix host=192.168.18.21/home/ideapadhdd, ignoring
[📦 md.obsidian.Obsidian ~]$

mmm interesting... I mean using /run/user/1000/gvfs works fine so.... for my use case its enough lol, but is there any way to only give access to a specific directory inside the sftp server??

@rusty-snake
Copy link

rusty-snake commented Sep 1, 2024

flatpak run --command=sh --filesystem=~/foo\\:bar org.gnome.TextEditor seems to work although being undocumented.

Now the question, does flatseal support this syntax?

@thepragmaticmero
Copy link
Author

ohhh double backslash, interesting.
On flatseal it keeps appearing as "This is not a valid option", so it's a bug that needs to be solved then. If it's not a feature bug, it is a UI bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants