• 39 Posts
  • 28 Comments
Joined 1 year ago
Cake day: June 13th, 2023
  • wile_e8@lemmy.worldOPtoAlbuquerque, NM@lemmy.world•Ski Santa Fe set to open on Thanksgiving with new tech
    1·
    1 year ago

    I know this isn’t technically ABQ, but I drive up to Ski Santa Fe multiple times each winter and I’m guessing other people in this community do as well. The new technology mentioned in this article made it interesting to me.

    The RFID passes aren’t a big deal, but they are kind of nice. They could be finicky when trying to get on the lift when I had them at Red River, no better or worse than having someone manually scan passes. But being able to reload them without visiting the ticket office in the morning was great.

    But this is the first time I’ve heard about the high-speed detachable lifts coming to Santa Fe, and I’m really looking forward to that even though it won’t be there until next winter. I’ve only gotten to try them once, in Winter Park, CO, and spending half as much time sitting on a lift makes the day so much better.

  • wile_e8@lemmy.worldtoLinux@lemmy.ml•The Flaws of Flatpak - What do you think about Flatpak Security?
    3·
    1 year ago

    OK, so I looked though my browser history, and here are some relevant pages I found:

    I don’t remember how much I used each one, but eventually I pieced together enough information information to get the Browserpass extension working in the Google Chrome flatpak. But three of those links are KeePassXC, which should be useful for adapting this for your use.

    The main file that was having problems was the Browserpass Native Messaging Hosts file in my config directory for the Chrome flatpak, ~/.var/app/com.google.Chrome/config/google-chrome/NativeMessagingHosts/com.github.browserpass.native.json. Originally it was a symlink to a file at /usr/lib/browserpass/hosts/chromium/com.github.browserpass.native.json:

    {
    "name": "com.github.browserpass.native",
    "description": "Browserpass native component for the Chromium extension",
    "path": "/usr/bin/browserpass-linux64",
    "type": "stdio",
    "allowed_origins": [
        "chrome-extension://naepdomgkenhinolocfifgehidddafch/"
    ]
}

    The call to /usr/bin/browserpass-linux64 did not see to work for me, so I ended up making a copy of the file in the NativeMessagingHosts directory and modified it to point to a script in my home mount:

    wile_e8 NativeMessagingHosts $ diff com.github.browserpass.native.json.orig com.github.browserpass.native.json
4c4
<     "path": "/usr/bin/browserpass-linux64",
---
>     "path": "/home/wile_e8/.config/browserpass/browserpass.sh",

    I don’t remember why I picked to do it inside the ~/.config directory, but it worked so I left it. And here is the script I put at ~/.config/browerpass/browserpass.sh:

    #!/bin/sh
cd ~
/usr/bin/flatpak-spawn --host /usr/bin/browserpass-linux64 2>/tmp/error.log

    I don’t remember how I came up with that script, it must be somewhere in the four links at the top.

    Finally, I needed to use Flatseal to allow access to the script. In the Google Chrome settings, under “Filesystem->Other files”, I added an entry saying ~/.config/browserpass:ro. Also modified from the default in Flatseal, I have “Filesystem->All user files” enabled, along with “Socket->D-Bus session bus” and “Socket->D-Bus system bus”. I don’t know how necessary the last three are, but I’m not messing with it now that I have it working.

    So, that’s what I did to get the Browserpass extension working in the Google Chrome flatpak. You’ll have to modify some things to get it working for KeePassXC, or for Firefox. But that general pattern should work.