Jump to content
Enpass Discussion Forum

mhaeuser

Members
  • Posts

    1
  • Joined

  • Last visited

mhaeuser's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • First Post Rare

Recent Badges

0

Reputation

  1. Good day everyone, good day @Vinod Kumar, I attempted to do the same with the Flatpak format for usage on Fedora Silverblue. It turns out the usage of "lsof" mentioned earlier is mostly incompatible with Flatpak as a whole [1], as the host "/proc" folder queried is never shared with any Flatpak. The only form of sharing I did find is child-parent Flatpaks [2], which would require the browser (and thus the Enpass extension) to be a child process Flatpak of the Enpass flatpak (which queries "/proc" via "lsof"). This doesn't only violate the sandbox, it's vastly impractical to enforce this relation. I did not test whether this would work in practice at all. As Enpass is proprietary, I can neither efficiently fix the issue myself, nor even provide a proposal right now as there is no information on how it works. "netstat" was mentioned above, but I'm quite sure one of my setups does not even have it, and yet Enpass works with the browser extension. "lsof" on the other hand is a package dependency, at the very least for Fedora. Of course it'd be ideal if you could just drop the dependency on "lsof" somehow, but if you could provide further information on what for and how exactly those tools are used, I could maybe try to come up with a workaround at some point. Thank you! Best regards, Marvin [1] https://github.com/flatpak/flatpak/issues/4001 [2] https://github.com/flatpak/flatpak/commit/62797b4be9b06de19639ca881c57fb9a15db190f ; https://docs.flatpak.org/en/latest/flatpak-command-reference.html (--parent-expose-pids)
×
×
  • Create New...