• 1 Post
  • 21 Comments
Joined 10 months ago
cake
Cake day: June 21st, 2024

help-circle








  • Just one open source example … freeradius has an option to log passwords:

    log {
        destination = files
        auth = no
        auth_badpass = no
        auth_goodpass = no
    }
    

    Or another example: The apache web server has a module that dumps all POST data, with passwords, in plain text:

    mod_dumpio allows for the logging of all input received by Apache and/or all output sent by Apache to be logged (dumped) to the error.log file. The data logging is done right after SSL decoding (for input) and right before SSL encoding (for output). As can be expected, this can produce extreme volumes of data, and should only be used when debugging problems.

    I don’t agree that this is “absolutely malice”, it could also be stupidity and forgetfulness.





  • The linked essay is quite long and (at least for me) hard to read. One of the first links in the article is to this patreon blog post, that summarizes the issue well.

    As we first announced last year, Apple is requiring that Patreon use their in-app purchasing system and remove all other billing systems from the Patreon iOS app by November 2024.

    This has two major consequences for creators:

    1. Apple will be applying their 30% App Store fee to all new memberships purchased in the Patreon iOS app, in addition to anything bought in your Patreon shop.
    2. Any creator currently on first-of-the-month or per-creation billing plans will have to switch over to subscription billing to continue earning in the iOS app, because that’s the only billing type Apple’s in-app purchase system supports.

    Before we go any further, we want to be crystal clear about one thing: Apple’s fee will not impact your existing members. It will only affect new memberships purchased in the iOS app from November onward.