• 0 Posts
  • 68 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle
  • Reverse proxies aren’t DNS servers.

    The DNS server will be configured to know that your domain, e.g., example.com or *.example.com, is a particular IP, and when someone navigates to that URL it tells them the IP, which they then send a request to.

    The reverse proxy runs on that IP; it intercepts and analyzes the request. This can be as simple as transparently forwarding jellyfin.example.com to the specific IP (could even be an internal IP address on the same machine - I use Traefik to expose Docker network IPs that aren’t exposed at the host level) and port, but they can also inspect and rewrite headers and other request properties and they can have different logic depending on the various values.

    Your router is likely handling the .local “domain” resolution and that’s what you’ll need to be concerned with when configuring AdGuard.


  • It isn’t, because their business practices violate the four FOSS essential freedoms:

    1. The freedom to run the program for any purpose
    2. The freedom to study and modify the program
    3. The freedom to redistribute copies of the original or modified program
    4. The freedom to distribute modified versions of the program

    Specifically, freedom 4 is violated, because you are not permitted to distribute a modified version of the program that connects to the Signal servers (even if all your modified version does is to remove Google Play Services or something similar).


  • This particular scenario involves the MacOS desktop app, not the phone app. The link is showing just an image for me - I think it’s supposed to be to https://stackdiary.com/signal-under-fire-for-storing-encryption-keys-in-plaintext/

    That said, let’s compare how it works on the phone to how it could work on MacOS and how it actually works on MacOS. In each scenario, we’ll suppose you installed an app that has hidden malware - we’ll call it X (just as a placeholder name) - and compare how much data that app has access to. Access to session data allows the app to spoof your client and send+receive messages

    On the phone, your data is sandboxed. X cannot access your Signal messages or session data. ✅ Signal may also encrypt the data and store an encryption key in the database, but this wouldn’t improve security except in very specific circumstances (basically it would mean that if exploits were being used to access your data, you’d need more exploits if the key were in the keychain). Downside: On iOS at least, you also don’t have access to this data.

    On MacOS, it could be implemented using sandboxed data. Then, X would not be able to access your Signal messages or spoof your session unless you explicitly allowed it to (it could request access to it and you would be shown a modal). ✅ Downside: the UX to upload attachments is worse.

    It could also be implemented by storing the encryption key in the keychain instead of in plaintext on disk. Then, X would not be able to access your Signal messages and session data. It might be able to request access - I’m not sure. As a user, you can access the keychain but you have to re-authenticate. ✅ Downside: None.

    It’s actually implemented by storing the encryption key in plaintext, collocated with the encrypted database file. X can access your messages and session data. ❌

    Is it foolproof? No, of course not. But it’s an easy step that would probably take an hour of dev time to refactor. They’re even already storing a key, just not one that’s used for this. And this has been a known issue that they’ve refused to fix for several years. Because of their hostile behavior towards forks, the FOSS community also cannot distribute a hardened version that fixes this issue.





  • They aren’t. From a comment on https://www.reddit.com/r/ublock/comments/32mos6/ublock_vs_ublock_origin/ by u/tehdang:

    For people who have stumbled into this thread while googling “ublock vs origin”. Take a look at this link:

    http://tuxdiary.com/2015/06/14/ublock-origin/

    "Chris AlJoudi [current owner of uBlock] is under fire on Reddit due to several actions in recent past:

    • In a Wikipedia edit for uBlock, Chris removed all credits to Raymond [Hill, original author and owner of uBlock Origin] and added his name without any mention of the original author’s contribution.
    • Chris pledged a donation with overblown details on expenses like $25 per week for web hosting.
    • The activities of Chris since he took over the project are more business and advertisement oriented than development driven."

    So I would recommend that you go with uBlock Origin and not uBlock. I hope this helps!

    Edit: Also got this bit of information from here:

    https://www.reddit.com/r/chrome/comments/32ory7/ublock_is_back_under_a_new_name/

    TL;DR:

    • gorhill [Raymond Hill] got tired of dozens of “my facebook isnt working plz help” issues.
    • he handed the repository to chrismatic [Chris Aljioudi] while maintaining control of the extension in the Chrome webstore (by forking chrismatic’s version back to himself).
    • chrismatic promptly added donate buttons and a “made with love by Chris” note.
    • gorhill took exception to this and asked chrismatic to change the name so people didn’t confuse uBlock (the original, now called uBlock Origin) and uBlock (chrismatic’s version).
    • Google took down gorhill’s extension. Apparently this was because of the naming issue (since technically chrismatic has control of the repo).
    • gorhill renamed and rebranded his version of ublock to uBlock Origin.

  • Say I go to a furniture store and buy a table. It has a 5 year warranty. 2 years later, it breaks, so I call Ubersoft and ask them to honor the warranty and fix it. If they don’t, then I can file a suit against them, i.e., for breach of contract. I may not even have to file a suit, as there may be government agencies who receive and act on these complaints, like my local consumer protection division.

    I’m talking about real things here. Your example is a situation where the US government agrees that a company shouldn’t be permitted to take my money and then renege on their promises. And that’s generally true of most governments.

    Supposing an absence of regulations protecting consumers like me, like you’re trying to suggest in your example, then it would be reasonable to assume an absence of laws and regulations protecting the corporation from consumers like me. Absent such laws, a consumer would be free to take matters into their own hands. They could go back to Ubersoft and take a replacement table without their agreement - it wouldn’t be “stealing” because it wouldn’t be illegal. If Ubersoft were closed, the consumer could break in. If Ubersoft security tried to stop them, the consumer could retaliate - damaging Ubersoft’s property, physically attacking the owner / management / employees, etc… Ubersoft could retaliate as well, of course - nothing’s stopping them. And as a corporation, they certainly have more power than a random consumer - but at that point they would need to employ their own security forces rather than relying on the government for them.

    Even if we kept laws prohibiting physical violence, the consumer is still regulated by things like copyright and IP protections, e.g., the anti-circumvention portion of the DMCA. Absent such regulations, a consumer whose software was rendered unusable or changed in a way they didn’t like could reverse engineer it, bypass DRM, host their own servers, etc… Given that you didn’t speak against those regulations, I can only infer that you are not opposed to them.

    Why do you think we don’t need regulations protecting consumers but that we do need regulations restricting them?



  • ultimately the market is behaving as if the threats are sincere so whether or not Valve would follow through is irrelevent to whether the presence of a policy is an exhibition of monopolistic power

    Courts have interpreted the anti-monopoly portion of the Sherman act, which governs antitrust law in the US, to mean that monopoly is only unlawful if the power is used in an unlawful way or if the monopoly was acquired through unlawful means.

    The need to see an actual example of a game being delisted for violation of the policy is a weirdly high standard of evidence

    As a smoking gun, I don’t think it’s unreasonable to ask for something like that.

    If it’s a policy Valve denies and the only evidence of it existing is a single reply in a forum somewhere, then yes, I’m skeptical. And given that there are examples of companies that were willing to break explicit, defensible policies, why aren’t there examples of companies who broke these? Unless the plaintiffs bring in multiple witnesses to testify that this was the policy communicated to them or something along those lines, I can’t see the evidence that they did have this policy being more compelling than the fact that there’s a complete lack of evidence that they ever acted on it.

    To be clear, I’m not saying Valve needs to have said that was the reason. But it certainly needs to look like that was the reason. If Valve can’t provide a valid reason for the termination, then that’s very compelling, and even if they can, it’ll come down to which is more believable.


  • Thank you! That document is exactly the sort of thing I was looking for. Just realized (after writing most of this comment) that it’s for Wolfire and not Vicki Shotbolt’s case, but the commentary’s still relevant, I think.

    There’s enough there that they may have a legitimate case, but there’s also a lot that is, as far as I know, completely acceptable for Valve to do. The specific items you listed, as well as a couple before / after them, are the most promising, IMO, but even so, there are a couple different counter-arguments that I could see Valve making.

    The first counter-argument would be that the comments in 204-205 were in the context of publishers who had already received Steam keys for the games in question and did not apply to games where the publisher had not received Steam keys.

    The second counter-argument would be that Tom Giardino was not speaking to Valve’s actual policy and/or that he was making empty threats that he didn’t have the power to enforce. Tom’s still with Valve (according to https://www.valvesoftware.com/en/people) so they wouldn’t be able to show that he was fired for giving publishers incorrect information, but it would be feasible for them to have record of him having gotten disciplinary action or something along those lines. Without something like that it’s much less credible stance, but not unbelievable - they’d basically have to be admitting negligence since this is a record of the actions of a representative their company. My gut says they were at least complicit.

    200 says Valve “insisted” a publisher change their price on the Discord Store but doesn’t indicate any enforcement action was taken. At first glance, 209 appeared to apply, but it, too, involves the sale of Steam keys. 230 goes into a bit more detail about 209.

    I read through the filing and still don’t see any instances of a game being delisted because it was being sold for cheaper elsewhere, when Steam keys weren’t in play. A lack of enforcement action against publishers not using Steam keys who set a different price in another storefront would go a long way toward showing that Valve’s policy was only relevant when the publishers were using Steam keys.

    In either case, Valve will need to make the argument that it is not anti-competitive to require publishers to agree to these terms when requesting free Steam keys.

    The arguments regarding DLC exclusivity (172-184) are another area where Valve might be found to be anti-competitive. That said, I don’t think exclusive DLCs benefit consumers and I would expect Valve to argue that the intent and impact of requiring DLC be published on their platform is for consumers’ benefit. I think proving something here would be dependent on the pricing angle.

    I still think Valve could argue that the intent and impact of their pricing decisions are to the benefit of consumers. The specific enforcement actions brought up were all in relation to the price of Steam keys on third-party storefronts, which I think will be held to a much lower standard than restricting the price of the game on other platforms. After all, the benefits of Steam keys aren’t intrinsic to Steam, and other platforms are free to offer a similar benefit to game publishers.

    In 191, the plaintiff shows that a publisher could set the price on a rival platform at 20% less and make more profit than on Steam. However, there aren’t any examples of enforcement actions where the discount on a rival platform did not exceed a 20% difference. Ultimately, if they don’t have at least that - optimally for a game whose publisher didn’t ever receive free Steam keys - the singular statement of one of their representatives might be the only concrete evidence they have. And at that point, the argument that Tom was just making empty threats has a lot more weight.


  • The article also says

    The first point is one we’ve heard repeated many times before, but there’s never been any proof on it. Which perhaps the Wolfire lawsuit and this may actually bring to light. An accusation doesn’t necessarily mean they’re right though. Something people get confused on often is Steam Keys, which are completely separate to Steam Store purchases.

    Saying “Don’t sell Steam keys off-platform for more than X% less than the game is priced for on Steam” and “Don’t sell your game elsewhere for more than X% less than the game is priced for on Steam“ are very different things. Steam openly does the former; I’ve never heard a reputable report of them doing the latter. The Wolfire lawsuit is explicitly about the former practice, for example.

    The press release for this lawsuit reads like it’s about the latter, but I suspect that’s solely for optics. I reviewed the website dedicated to the lawsuit (steamyouoweus.co.uk) and thought they might have some more concrete evidence - nope, nothing. Under the first question in FAQs they have a link to their key documents, but the documents are “coming soon.”

    Until they actually substantiate their claim, this lawsuit is just noise.


  • That’s still a single point of failure.

    So is TLS or the compromise of a major root certificate authority, and those have no bearing on whether an approach qualifies as using 2FA.

    The question is “How vulnerable is your authentication approach to attack?” If an approach is especially vulnerable, like using SMS or push notifications (where you tap to confirm vs receiving a code that you enter in the app) for 2FA, then it should be discouraged. So the question becomes “Is storing your TOTP secrets in your password manager an especially vulnerable approach to authentication?” I don’t believe it is, and further, I don’t believe it’s any more vulnerable than using a separate app on your mobile device (which is the generally recommended alternative).

    What happens if someone finds an exploit that bypasses the login process entirely?

    Then they get a copy of your encrypted vault. If your vault password is weak, they’ll be able to crack it and get access to everything. This is a great argument for making sure you have a good vault password, but there are a lot of great arguments for that.

    Or do you mean that they get access to your logged in vault by compromising your device? That’s the most likely worst case scenario, and in such a scenario:

    • all of your logged in accounts can be compromised by stealing your sessions
    • even if you use a different app for your 2FA, those TOTP secrets and passkeys can be stolen - they have to be on a different device
    • you’re also likely to be subject to a ransomware attack

    In other words, your only accounts that are not vulnerable in this situation solely because their TOTP secret is on a different device are the ones you don’t use on that device in the first place. This is mostly relevant if your computer is compromised - if your phone is compromised, then it doesn’t matter that you use a separate password manager and authenticator app.

    If you use an account on your computer, since it can be compromised without having the credentials on device, you might as well have the credentials on device. If you’re concerned about the device being compromised and want to protect an account that you don’t use on that device, then you can store the credentials in a different vault that isn’t stored on your device.

    Even more common, though? MITM phishing attacks. If your password manager verifies the url, fills the password, and fills your TOTP, then that can help against those. Start using a different device and those protections fall away. If your vault has been compromised and your passwords are known to an attacker, but they don’t have your TOTP secrets, you’re at higher risk of erroneously entering them into a phishing site.

    Either approach (same app vs different app) has trade-offs and both approaches are vulnerable to different sorts of attacks. It doesn’t make sense to say that one counts as 2FA but the other doesn’t. They’re differently resilient - that’s it. Consider your individual threat model and one may be a better option than the other.

    That said, if you’re concerned about the resiliency of your 2FA approach, then look into using dedicated security keys. U2F / WebAuthn both give better phishing resistance than a browser extension filling a password or TOTP can, and having the private key inaccessible can help mitigate device compromise concerns.




  • I haven’t worked with Scribus but I’ve heard good things about it, so I don’t think you’d be making a wrong choice by going with it. For this use case, the main reasons I can think of for why LaTeX would be preferable would be:

    • if you preferred working with it, or with a particular LaTeX tool
    • if you want to learn one tool or the other
    • if being able to write a script to create the output is something you want to do and the equivalent is not possible in Scribus


  • If you use that docker compose file, I recommend you comment out the build section and uncomment the image section in the lemmy service.

    I also recommend you use a reverse proxy and Docker networks rather than exposing the postgres instance on port 5433, but if you aren’t familiar with Docker networks you can leave it as is for now. If you’re running locally and don’t open that port in your router’s firewall, it’s a non-issue unless there’s an attacker on your LAN, but given that you’re not gaining anything from exposing it (unless you need to connect to the DB directly regularly - as a one off you could temporarily add the port mapping), it doesn’t make sense to increase your attack surface for no benefit.



  • I haven’t personally used any of these, but looking them over, Tipi looks the most encouraging to me, followed by Yunohost, based largely on the variety of apps available but also because it looks like Tipi lets you customize the configuration much more. Freedom Box doesn’t seem to list the apps in their catalog at all and their site seems basically useless, so I ruled it out on that basis alone.