[-] ken@discuss.tchncs.de 1 points 21 hours ago* (last edited 21 hours ago)
[-] ken@discuss.tchncs.de 2 points 1 day ago* (last edited 1 day ago)

This and the links it references are probably relevant:

https://github.com/keepassxreboot/keepassxc/issues/12779

[-] ken@discuss.tchncs.de 2 points 2 days ago* (last edited 1 day ago)

Thanks to you both! Can you explain, like you might to a three-year-old, why this is considered a bug?

Well, you are getting forwarded to an issue tracker for technical discussions. The context is people collaborating on the Firefox codebase. In this space, "bug" might not imply what you think it does. Like, new features still under development and general improvements are also tracked as "bugs" in Bugzilla. That doesn't mean that anything was considered broken.

With regards to where runtime files and data is stored, the Firefox (and therefore Librewolf) way of doing it is widely considered legacy at this point. They probably wouldn't build it that way if it was done from scratch today. But it comes from a different era. There is now heritage, legacy, and compatibility making the transition take years. That is normal and expected with a project as widely adopted and integrated as Firefox.

I think there is not much unique to Librewolf here (exception might be the librewolf.overrides.cfg); it's just inheriting and following upstream.

Old place: .librewolf. New place: Split between ~/.config/librewolf (config) and ~/.local/share/librewolf (data).

Here and now as an existing user who doesn't really want to care, I would advice sticking with the "old" current location of just ~/.librewolf and not moving things around or reconfiguring yourself. It's still being relied on by some parts of the browser. Depending on what features and addons you use, things might break if you expect to do a full move already.

See for example https://bugzilla.mozilla.org/show_bug.cgi?id=2005167

Some people feel strongly about "stay the F* out of my home directory, all you apps" and they might tell us this really is a Bug, how crazy it is that it isn't fixed yet, etc. Their concerns aren't relevant for a three-year old. Or even most people who just want their browser to work. They might actually help in pushing development forward and the platform getting on with the times. And they find and complain about the edge-cases so that step by step the transition becomes more seamless and complete. But bottom line is that calls for action are targeted at devs and maintainers; not users like yourself (really not meant as gate-keeping but more to point out that there's a depth and assumption of context here making it take some immersion to make sense of what's being said and choosing not to partake is fine).

[-] ken@discuss.tchncs.de 1 points 2 days ago* (last edited 2 days ago)

Whatever else you do, homelabbing and/or coding on private projects on the side will do you well. Try to go small. Holds at literally any level.

[-] ken@discuss.tchncs.de 1 points 3 days ago

Sounds like clients could do a better job in merging cross-posts and making it easier to filter them from the view.

[-] ken@discuss.tchncs.de 2 points 3 days ago* (last edited 2 days ago)

Been digging into the Tor Browser codebase recently and as a consequence now lifting over a few goodies in the privacy and security departments from there to Konform Browser

[-] ken@discuss.tchncs.de 1 points 4 days ago* (last edited 4 days ago)

Yes! And thanks for trying :)

As you do, it will help to know if you also tried Firefox (or other derivative) and if results there are same or different from Konform.

[-] ken@discuss.tchncs.de 1 points 4 days ago* (last edited 4 days ago)

When someone willing to package and test that shows up ;^^

In particular, being on flathub means someone with a github account needs to push it up (sorry i'm done there).

Here is a starting point: https://codeberg.org/konform-browser/flatpak

Happy to iterate on codeberg with anyone who wants to tackle this

22
submitted 4 days ago by ken@discuss.tchncs.de to c/linux@lemmy.world

Hi all!

Latest version of Konform Browser just dropped and now I come here to share with y'all about what's been cooking.

If you are new to Konform Browser, dev writing and previously posted on on this community introducing the project here.

Highlights since last time:

  • Latest security fixes from up to most recent Firefox ESR 140.7.1.
  • A new welcome screen (pictured) where user can quickly choose between how private vs integrated experience they want, from a locked down "Purely Private" all the way to an unleashed "Just Make It Work" (affectionately referred to as "yolo mode")
    • The "Show detailed information" link leads to a table showing exactly what settings will be impacted by each preset so user can make educated decision and understand impact before choosing.
  • Improvements around privacy and fingerprinting. In particular: Closed a significant vector of identity leaks and fingerprinting from unique IDs sent in Origin headers of HTTP requests by addons. This is a previously known issue (1405971) that has been considered wontfix by upstream for 6 years now.
    • To my knowledge, Konform Browser is the only Firefox derivative which protects against this under defaults and improves over status quo in chromium too. Attempts are being made to reach out and see if the patch can also be of interest and benefit for Tor Browser.
    • New user pref network.http.addonOriginBehavior can be tweaked to further change behavior and work around any breaking addons.
    • A future update might change default to 3 (random), which could make browser choice less fingerprintable. The current default is not set in stone and I'd be very curious about what breaks and what doesn't if anyone plays around with this.
  • Now also publishing binary packages for easy installation and updates from Alpine Linux and Arch Linux package repos, alongside deb/rpm ones. All builds and releases are produced by Codeberg CI. Building from source is of course still supported.
  • Various improvements and fixes for optional features unlocked by "Just Make It Work" preset

There is also now a more official fedi account on Mastodon where an abbreviated version of this post is already shared with a couple of screenshots of the new onboarding: @konform@techhub.social^1^.

As always, installation and build instructions can be found from release notes and doors are open on Codeberg for issue reports and merge requests alike.

https://codeberg.org/konform-browser/source/releases

^1^: Still figuring out how crossposting works or doesn't across the fedis! In case federation clients botcher the link: https://techhub.social/@konform

[-] ken@discuss.tchncs.de 6 points 4 days ago* (last edited 4 days ago)

Maybe you already figured this out but I think it's a common gotcha:

Wireguard AllowedIPs means just that: IP addresses that are allowed to be routed over the tunnel.

There is nothing that says that you need to have 1-to-1 mapping between that and actual routes. Most of the time it's what you want but there are situations where you want it different. Some people have a wider subnet for AllowedIPs but only add certain routes specifically.

wg-quick additionally adds corresponding ip routes as a convenience. systemd-networkd did at some point but don't anymore. I'm not sure what NetworkManager's Wireguard plugin is even supposed to be doing there these days. Most of the time what looks broken is actually a result of unclear documentation and a mismatch in assumptions between dev and user.

It's an understandable source of confusion and the tools don't always help when they try to.

[-] ken@discuss.tchncs.de 17 points 5 days ago* (last edited 5 days ago)

Just to be clear, most of these (think about egrep/fgrep for a moment) are deprecated and "shouldn't be used" in scripts for distribution. What's new is that you can't expect everyone else to have them and having dependency on them in shipped software is considered antipattern.

Nobody gives a shit what aliases and shims you use in your own shell.

On iptables: By now it's even gone from kernel and the turn tabled with the cli command now actually being a shim calling into its successor nft. IMO nft is much more approachable for beginners to pick up and the rules files become so much more readable and maintainable. If you're already committed to iptables syntax then cool - but with very few exceptions I don't think anyone needs to learn iptables today - just go straight to nft and you'll be happier for it. Similar for ifconfig.

[-] ken@discuss.tchncs.de 2 points 5 days ago

ip -br a, even

18
submitted 5 days ago by ken@discuss.tchncs.de to c/privacy@lemmy.ml

Hi all!

Latest version of Konform Browser just dropped and now I come here to share with y'all about what's been cooking.

If you are new to Konform Browser, dev writing and previously posted on Lemmy introducing the project here.

Highlights since last time:

  • Latest security fixes from up to most recent Firefox ESR 140.7.1.
  • A new welcome screen (pictured) where user can quickly choose between how private vs integrated experience they want, from a locked down "Purely Private" all the way to an unleashed "Just Make It Work" (affectionately referred to as "yolo mode")
    • The "Show detailed information" link leads to a table showing exactly what settings will be impacted by each preset so user can make educated decision and understand impact before choosing.
  • Improvements around privacy and fingerprinting. In particular: Closed a significant vector of identity leaks and fingerprinting from unique IDs sent in Origin headers of HTTP requests by addons. This is a previously known issue (1405971) that has been considered wontfix by upstream for 6 years now.
    • To my knowledge, Konform Browser is the only Firefox derivative which protects against this under defaults and improves over status quo in chromium too. Attempts are being made to reach out and see if the patch can also be of interest and benefit for Tor Browser.
    • New user pref network.http.addonOriginBehavior can be tweaked to further change behavior and work around any breaking addons.
    • A future update might change default to 3 (random), which could make browser choice less fingerprintable. The current default is not set in stone and I'd be very curious about what breaks and what doesn't if anyone plays around with this.
  • Now also publishing binary packages for easy installation and updates from Alpine Linux and Arch Linux package repos, alongside deb/rpm ones. All builds and releases are produced by Codeberg CI. Building from source is of course still supported.
  • Various improvements and fixes for optional features unlocked by "Just Make It Work" preset

There is also now a more official fedi account on Mastodon where an abbreviated version of this post is already shared with a couple of screenshots of the new onboarding: @konform@techhub.social^1^.

As always, installation and build instructions can be found from release notes and doors are open on Codeberg for issue reports and merge requests alike.

https://codeberg.org/konform-browser/source/releases

^1^: Still figuring out how crossposting works or doesn't across the fedis! In case federation clients botcher the link: https://techhub.social/@konform


Cross-post. Original Thread @ https://discuss.tchncs.de/post/54998565?scrollToComments=true

[-] ken@discuss.tchncs.de 3 points 5 days ago* (last edited 5 days ago)

still pissed the name is not inspired on a canine/lupine

I kind of want to keep that subtle but it is there :p

Follow-up hint: In Japan they sound different than in Norway

Good to know on the crossposting. And thanks for encouragement! If winds are willing we can also land a patch for this in Tor Browser (and I guess consequentially Mullvad). Only feels fair to try contributing back since we are effectively benefiting from their contributions and if we get reviewing eyes on code in process it's win-win.

17

Hi all!

Latest version of Konform Browser just dropped and now I come here to share with y'all about what's been cooking.

If you are new to Konform Browser, dev here and previously posted on Lemmy introducing the project here.

Highlights since last time:

  • Latest security fixes from up to most recent Firefox ESR 140.7.1.
  • A new welcome screen (pictured) where user can quickly choose between how private vs integrated experience they want, from a locked down "Purely Private" all the way to an unleashed "Just Make It Work" (affectionately referred to as "yolo mode")
    • The "Show detailed information" link leads to a table showing exactly what settings will be impacted by each preset so user can make educated decision and understand impact before choosing.
  • Improvements around privacy and fingerprinting. In particular: Closed a significant vector of identity leaks and fingerprinting from unique IDs sent in Origin headers of HTTP requests by addons. This is a previously known issue (1405971) that has been considered wontfix by upstream for 6 years now.
    • To my knowledge, Konform Browser is the only Firefox derivative which protects against this under defaults and improves over status quo in chromium too. Attempts are being made to reach out and see if the patch can also be of interest and benefit for Tor Browser.
    • New user pref network.http.addonOriginBehavior can be tweaked to further change behavior and work around any breaking addons.
    • A future update might change default to 3 (random), which could make browser choice less fingerprintable. The current default is not set in stone and I'd be very curious about what breaks and what doesn't if anyone plays around with this.
  • Now also publishing binary packages for easy installation and updates from Alpine Linux and Arch Linux package repos, alongside deb/rpm ones. All builds and releases are produced by Codeberg CI. Building from source is of course still supported.
  • Various improvements and fixes for optional features unlocked by "Just Make It Work" preset

There is also now a more official fedi account on Mastodon where an abbreviated version of this post is already shared with a couple of screenshots of the new onboarding: @konform@techhub.social^1^. Since I couldn't figure out how to crosspost Mastodon -> Lemmy you get me rambling here instead ๐Ÿ˜˜

As always, installation and build instructions can be found from release notes and doors are open on Codeberg for issue reports and merge requests alike.

https://codeberg.org/konform-browser/source/releases

^1^: In case federation clients botcher the link: https://techhub.social/@konform

16
submitted 6 days ago* (last edited 6 days ago) by ken@discuss.tchncs.de to c/privacy@lemmy.dbzer0.com

Hi all!

Latest version of Konform Browser just dropped and now I come here to share with y'all about what's been cooking.

If you are new to Konform Browser, dev here and previously posted on this community introducing the project here.

Highlights since last time:

  • Latest security fixes from up to most recent Firefox ESR 140.7.1.
  • A new welcome screen (pictured) where user can quickly choose between how private vs integrated experience they want, from a locked down "Purely Private" all the way to an unleashed "Just Make It Work" (affectionately referred to as "yolo mode")
    • The "Show detailed information" link leads to a table showing exactly what settings will be impacted by each preset so user can make educated decision and understand impact before choosing.
  • Improvements around privacy and fingerprinting. In particular: Closed a significant vector of identity leaks and fingerprinting from unique IDs sent in Origin headers of HTTP requests by addons. This is a previously known issue (1405971) that has been considered wontfix by upstream for 6 years now.
    • To my knowledge, Konform Browser is the only Firefox derivative which protects against this under defaults and improves over status quo in chromium too. Attempts are being made to reach out and see if the patch can also be of interest and benefit for Tor Browser.
    • New user pref network.http.addonOriginBehavior can be tweaked to further change behavior and work around any breaking addons.
    • A future update might change default to 3 (random), which could make browser choice less fingerprintable. The current default is not set in stone and I'd be very curious about what breaks and what doesn't if anyone plays around with this.
  • Now also publishing binary packages for easy installation and updates from Alpine Linux and Arch Linux package repos, alongside existing deb/rpm ones. Building from source is of course still supported.
  • Various improvements and fixes for optional features unlocked by "Just Make It Work" preset

There is also now a more official fedi account on Mastodon where an abbreviated version of this post is already shared with a couple of screenshots of the new onboarding: @konform@techhub.social^1^. Since I couldn't figure out how to crosspost Mastodon -> Lemmy you get me rambling here instead ๐Ÿ˜˜

As always, installation and build instructions can be found from release notes and doors are open on Codeberg for issue reports and merge requests alike.

https://codeberg.org/konform-browser/source/releases

^1^: In case federation clients botcher the link: https://techhub.social/@konform

31
submitted 3 weeks ago by ken@discuss.tchncs.de to c/foss@beehaw.org

Hi Beehaw people! New here and hope some of you will take interest in this toolkit and accompanying writeup. :3


Set up a framework to fully man-in-the-middle my own browsers' networking and see what they're up to beyond just looking at their DNS queries and encrypted tcp packets. We force the browser to trust our mitmproxy cacert so we can peek inside cleartext traffic and made it conveniently reproducible and extensible.

It has containers for official Firefox, its Debian version, and some other FF derivatives that market a focus on privacy or security. Might add a few more of those or do the chromium family later - if you read the thing and want more then please let us know what you want to see under the lens in a future update!

Tests were run against a basic protocol for each of them and results are aggregated at the end of the post.


Apart from testing browsers themselves it can be useful for putting extensions under the lens. Making a modern browser properly accept a proxy and trust the mitmproxy cert is a lot more obscure and fiddly than it might seem so hopefully this can be helpful in empowering and pushing other people to peek inside what's actually going on inside their own systems without spending hours or days figuring out what actually makes it tick.

Rewritten cross-post. First Thread @ https://discuss.tchncs.de/post/53845514

15

Set up a framework to fully man-in-the-middle my own browsers' networking and see what they're up to beyond just looking at their DNS queries and encrypted tcp packets. We force the browser to trust our mitmproxy cacert so we can peek inside cleartext traffic and made it conveniently reproducible and extensible.

It has containers for official Firefox, its Debian version, and some other FF derivatives that market a focus on privacy or security. Might add a few more of those or do the chromium family later - if you read the thing and want more then please let us know what you want to see under the lens in a future update!

Tests were run against a basic protocol for each of them and results are aggregated at the end of the post.

Posting with ambition that this can trigger some follow-ups sharing derived or similar things. Maybe someone could make a viral blog post by doing some deeper tests and making their results digestible ;)


Cross-post. Original Thread @ https://discuss.tchncs.de/post/53845514

51
submitted 3 weeks ago by ken@discuss.tchncs.de to c/privacy@lemmy.ml

Set up a framework to fully man-in-the-middle my own browsers' networking and see what they're up to beyond just looking at their DNS queries and encrypted tcp packets. We force the browser to trust our mitmproxy cacert so we can peek inside cleartext traffic and made it conveniently reproducible and extensible.

It has containers for official Firefox, its Debian version, and some other FF derivatives that market a focus on privacy or security. Might add a few more of those or do the chromium family later - if you read the thing and want more then please let us know what you want to see under the lens in a future update!

Tests were run against a basic protocol for each of them and results are aggregated at the end of the post.

Posting with ambition that this can trigger some follow-ups sharing derived or similar things. Maybe someone could make a viral blog post by doing some deeper tests and making their results digestible ;)


Cross-post. Original Thread @ https://discuss.tchncs.de/post/53845514

23
submitted 3 weeks ago* (last edited 3 weeks ago) by ken@discuss.tchncs.de to c/privacy@lemmy.ca

Set up a framework to fully man-in-the-middle my own browsers' networking and see what they're up to beyond just looking at their DNS queries and encrypted tcp packets. We force the browser to trust our mitmproxy cacert so we can peek inside cleartext traffic and made it conveniently reproducible and extensible.

It has containers for official Firefox, its Debian version, and some other FF derivatives that market a focus on privacy or security. Might add a few more of those or do the chromium family later - if you read the thing and want more then please let us know what you want to see under the lens in a future update!

Tests were run against a basic protocol for each of them and results are aggregated at the end of the post.

Posting with ambition that this can trigger some follow-ups sharing derived or similar things. Maybe someone could make a viral blog post by doing some deeper tests and making their results digestible ;)

66
submitted 3 weeks ago* (last edited 3 weeks ago) by ken@discuss.tchncs.de to c/linux@lemmy.world

Good time-of-day, Linux users! I hope you will take kindly^1^ to coming here to tell you about Konform Browser and what it is. And also ask you to try it out in case this is your cup of tea :)

In short, Konform Browser is a web browser with the goal of promoting user freedom and access to the rights of security, privacy and anonymity. It is intended as a general-purpose browser fit both for daily online surfing as well as targeted deployments in secure or untrusted environments. It is fundamentally a patched build and custom configuration of Mozilla FireFox ESR. It started as a fork of LibreWolf and now stands on its own four feet.

Some highlights to give an idea to those familiar with LibreWolf or other FF fork:

  • Security: Konform is based on Firefox ESR instead of Rapid Release. This means a more stable base without missing out on the latest security updates, in exchange for longer time waiting for the newest features from Firefox. It also enables shorter lead times to backport upstream updates.
    • In this sense (and a few others), Konform Browser is closer to IceCat/GNUZilla than it is to Librewolf.
  • Freedom: Konform allows a higher level of customization. It gives the user control and trusts you with that responsibility. Some examples:
    • Allows enabling dark mode and following system theming even when Resist Fingerprinting is enabled
    • Allows installing your own self-built unsigned add-ons
    • "Spoof referer source" user configuration option
  • Privacy and security: Disables all browser features relying on external network connections.
    • "RemoteSettings" is completely disabled^2^.
    • No cloud "AI" integrations. You can run Konform on a disconnected network and not notice any reduced functionality.
    • All telemetry, metrics, and ads from the browser disabled.
    • OCSP turned off (but we have CRLite).
    • tcpdump and see the difference!

I should add that even if we contrast with LibreWolf above, this is not at all meant as a dig or criticism. I think they have done and continue to do great contributions for the benefit of all of us. That we chose it as upstream and that it's the easiest to compare with is a testament both to how closely aligned we are and that Konform has a lot to thank Librewolf and the wider Firefox customization community for. Like they built from Librefox and Arkenfox to bring private browsing to a wider audience, so are we but the next to try help widen and deepen the browser ecosystem.

The recommended installation method is building from source but there are also binary packages for x86_64 and arm64 built by Codeberg CI. Currently Linux only, considering Android next and could use some assistance with that.

Doors open for users, testers and contributors. Looking forward to hear what you think and if there's anything missing!

^1^: Disclosure: Am dev. This is a rewritten crosspost.

^2^: This means that local full-page translation is also unavailable even if in principle it should be possible to bundle and run translations fully locally. It's just the way Mozilla built it. Patches towards allowing users to enable fully offline translations would be very welcome.


Sources: https://codeberg.org/konform-browser

Deb / RPM / Tarball / Container image

See releases for details.

Arch User Repo package

Arch User Repo binary package

Screenshot

73
submitted 1 month ago* (last edited 4 weeks ago) by ken@discuss.tchncs.de to c/privacy@lemmy.dbzer0.com

There is a new Firefox fork in town: Konform Browser. Its focus is privacy, security and user freedom. Yes, I know this sounds familiar - but hear me out, I do think we have something to bring to the table!

The project started as a fork of LibreWolf and now stands on its own four feet.

Some highlights to give an idea to those familiar with LibreWolf or other FF fork:

  • Security: Konform is based on Firefox ESR. This means a more stable base without missing out on the latest security updates, in exchange for longer time waiting for the newest features from Firefox. It also enables shorter lead times to backport upstream updates.
    • In this sense (and a few others), Konform Browser is closer to IceCat/GNUZilla than it is to Librewolf.
  • Freedom: Konform allows a higher level of customization. It gives the user control and trusts you with that responsibility. Some examples:
    • Allows enabling dark mode and following system theming even when Resist Fingerprinting is enabled.
    • Allows installing your own self-built unsigned add-ons
    • "Spoof referer source" user configuration option
  • Privacy and security: Disables all browser features relying on external network connections.
    • "RemoteSettings" is completely disabled^1^.
    • No cloud "AI" integrations. You can run Konform on a disconnected network and not notice any reduced functionality.
    • All telemetry, metrics, and ads from the browser disabled.
    • OCSP turned off (but we have CRLite).
    • tcpdump and see the difference

I should add that even if we contrast with LibreWolf above, this is not at all meant as a dig or criticism. That we chose it as base and that it's the easiest to compare with is a testament both to how closely aligned we are and that Konform has a lot to thank Librewolf and the wider Firefox customization community for. Like they built from Librefox and Arkenfox to bring private browsing to a wider audience, so are we but the next to try help widen and deepen the browser ecosystem.

The recommended installation method is building from source but there are also binary packages for x86_64 and arm64 built by Codeberg CI. Currently Linux only, considering Android next and could use some assistance with that.

Doors open for users, testers and contributors. Looking forward to hear what you think and if there's anything missing.

^1^: This means that local full-page translation is also unavailable even if in principle it should be possible to bundle and run translations fully locally. It's just the way Mozilla built it. Patches towards allowing users to enable fully offline translations would be very welcome.


Sources: https://codeberg.org/konform-browser

Arch User Repo package

Deb / RPM / Tarball

See releases for details.

Screenshot

17
submitted 1 month ago* (last edited 1 month ago) by ken@discuss.tchncs.de to c/unixporn@lemmy.world

Redmond97-SE is a living continuation of the now unmaintained Redmond 97.

"Redmond" style themes for GTK, Xfce, Metacity, WINE.

Includes both old-school retro variants to emulate Win9x/2000/XP, plus more modern darks for the productivity-focused desktop.

AUR packaging for Arch Linux just dropped.

48
submitted 1 month ago* (last edited 1 month ago) by ken@discuss.tchncs.de to c/unixporn@lemmy.world
  • Distribution: QubesOS 4.3
  • Desktop Environment: Xfce
  • Theme: Redmond97-SE
  • Window Manager: Xmonad
  • Terminal: xterm + tmux
  • Launcher: Rofi^1^
  • Bar: xfce4-panel

Windows

Top-left to bottom right:

  1. neovim "IDE" with integrated terminal editing dotfiles (Debian)
  2. dom0 admin terminal (Fedora)
  3. Qubes Manager looking at some templates (Fedora)
  4. Thunar File manager about to move a file between qubes (Whonix)
  5. Konform Browser browsing codeberg (Arch Linux)

Each app and window can belong to a separate qube (Xen VM), visually discriminated by differing color schemes.

Thanks to Ben Grandes qusal which was very helpful as base for setting things up.

This is a setup optimized for productivity and efficiency, which is reflected in the lack of eye-candy and gratuitous margins.

^1^: Not pictured - I figured the screenshot was busy enough. If y'all want to see more LMK.

view more: next โ€บ

ken

joined 1 month ago