Account in picture was banned within minutes of posting this information

    • PaX [comrade/them, they/them]@hexbear.net
      link
      fedilink
      English
      arrow-up
      24
      ·
      edit-2
      4 months ago

      Assuming all those substrings of usernames are split into different expressions like “EndWokeness” (without quotes ofc) it’s valid regex, it’s just an exact match

      Mainposting on main rn

        • PaX [comrade/them, they/them]@hexbear.net
          link
          fedilink
          English
          arrow-up
          12
          ·
          edit-2
          4 months ago

          A program that separates these out of that config file/representation/whatever this is (idk what Okta is tbh) into individual substrings is really easy

          I actually wrote a regex that matches each username in that structure for fun lol: (?<=[\[| ])[a-zA-Z0-9_]+ but you can match regex with regex too (It’s long as hell though, relatively)

          You can try it in your browser at: https://regex101.com/

          Idk why they called that field .*regex though, probably cuz it’s fake

          Wait I can write a better regex lol

          Edit: this will match all substrings properly inside that structure, including more regexes, correctly(edit edit: WRONG!): (?<=[\[| ])[^,]+(?=[,|\]])

          Edit edit: It’s all fucked and my brain hurts now because I wanted to match any valid regex inside of that structure, separately

          I will be back with the ultimate regex later, probably recursive and with the caveat that if you want to use comma literals, you will have to escape them, call that shit X-regex (special X.com regex syntax)

          I am going to bed I am so tired

          I’m sorry, there’s no way I can write this in a sane-sounding way, it’s been a journey and I’m probably drastically overcomplicating this

            • PaX [comrade/them, they/them]@hexbear.net
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              4 months ago

              I should not have said that, I’m sorry I was really tired, but I think it’s also more complicated than no

              Many implementations of “regular expressions” are actually capable of describing more than regular languages

              Like Perl/PCRE’s regular expression parser (which I used to write the above regexes) is capable of recursive evaluation and backreferences and probably other stuff I don’t know about cuz I don’t use it very often

              I don’t actually know if you can or not but yeah

              Tbh, you probably know more about formal language theory than me blob-no-thoughts

            • intensely_human
              link
              fedilink
              English
              arrow-up
              1
              ·
              4 months ago

              Dude what? This is bringing back flashbacks of trying to match nested parentheses.

              I can’t remember where or when it was. Are you telling me I was defeated by some impossible task back then?

        • PaX [comrade/them, they/them]@hexbear.net
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          4 months ago

          Hi, idk if you saw my other reply, but I have returned with the promised regular expression capable of doing this kitty-cri-potato (at least when parsed by PCRE and similar)

          (?<=(?<!\\)\[|(?<!\\), ).*?(?=(?<!\\)]|(?<!\\),)

          It will match each username/regex matching usernames as an individual substring

          In the end I didn’t need recursion and managed to accomplish the task by using nested lookarounds and making the assumption that brackets and commas are escaped with backslashes. It could probably be further simplified by using subroutines that some regex parsers are capable of using. Also it is most likely possible to write a regex that doesn’t require escaping brackets, besides when you need to escape brackets when writing regexes anyway ofc. The requirement that commas be escaped is analogous to requiring that quotes be escaped inside a string literal if instead the usernames/regexes that match usernames were enclosed in quotes

          I uhhhh don’t write many regexes blob-no-thoughts

          There’s probably something to be said about this task being easier to accomplish in languages “more powerful” (in chomsky-yes-honey terms: “Chomsky hierarchy”) than regular languages but I’m not chomsky-yes-honey (kamala-coconut-tree-free languages, etc contextphobic )

          I have a tendency toward owning myself, if you find a way to break my regex without breaking the assumptions specified above I will be further owned

          • footfaults [none/use name]@hexbear.net
            link
            fedilink
            English
            arrow-up
            3
            ·
            4 months ago

            Here’s the the thing. The snippet that was posted by that account is not any known format. It’s not YAML, it’s not INI syntax, it’s not JSON, or TOML, or anything that is a common configuration syntax. It’s not valid JS. It’s bullshit. It’s just close enough to programming code that it would maybe convince some people.

            So, while you spent a lot of time proving that you if you were forced to work with this file, there’s an incredibly nasty set of regex and parsing that you could do to make this actually work, there’s absolutely no reason why this would be done.

            • PaX [comrade/them, they/them]@hexbear.net
              link
              fedilink
              English
              arrow-up
              1
              ·
              4 months ago

              People rolling their own formats isn’t really that uncommon. And besides, that file is one s/ =/:/g away from being valid YAML. There might even be a YAML or TOML parser around that will accept this, idk

              there’s an incredibly nasty set of regex and parsing that you could do to make this actually work

              It only really looks nasty cuz I wanted to “parse” this file mentioning regex with regex for fun lol, it’s basically YAML

              The syntax of that file isn’t the sus part imo. I feel like I’m being an annoying pedant but yeah

          • footfaults [none/use name]@hexbear.net
            link
            fedilink
            English
            arrow-up
            3
            ·
            edit-2
            4 months ago

            I saw your comments. I was trying to get home and use my FreeBSD machine to reply since I was on mobile today and of course amdgpu decided to start causing kernel panics so it ate all my time. I’ll respond probably tomorrow evening.

            You’ve done enough work where it is worth having a full discussion instead of trying to type something up on my mobile device. It’s all good stuff, you put the work in

            • PaX [comrade/them, they/them]@hexbear.net
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              4 months ago

              Ohh, you’re good, I hope I didn’t make you feel pressured to reply or anything. Sometimes I just start writing and it ends up being a lot lol, besides I just like writing regular expressions sometimes lol

              Also 07 to another BSD user. I’m speaking to you with an OpenBSD machine rn lol. I hope you got your kernel panicking fixed

              Post stack trace here if you want help perhaps, I’ve also had to debug BSD kernels before (although the graphics stuff is mostly ripped straight from Linux lol)

  • GaveUp [she/her]@hexbear.net
    link
    fedilink
    English
    arrow-up
    41
    ·
    4 months ago

    Fakest config file I’ve ever seen. I ain’t gonna explain it but it’s way too shit for Okta to have created a custom internal format like this

  • combat_brandonism [they/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    37
    ·
    edit-2
    4 months ago

    I don’t think okta mainly works like this (it’s an internal company account SSO software provider, not something you’d use for your user’s accounts), so this is instantly sus. Happy to be wrong though but be careful sharing this around until there’s more info.

  • CoolerOpposide [none/use name]@hexbear.net
    link
    fedilink
    English
    arrow-up
    10
    ·
    4 months ago

    And where did that bring you?

    back-to-me-shining

    For the bourgeoisie, freedom of the press meant freedom for the rich to publish and for the capitalists to control the newspapers, a practice which in all countries, including even the freest, produced a corrupt press…

    The publication of a newspaper is a big and profitable capitalist undertaking in which the rich invest millions upon millions of rubles. “Freedom of the press” in bourgeois society means freedom for the rich systematically, unremittingly, daily, in millions of copies, to deceive, corrupt and fool the exploited and oppressed mass of the people, the poor. This is the simple, generally known, obvious truth which everyone sees and realises but which “almost everyone” “bashfully” passes over in silence, timidly evades.

    Look at Russkoye Slovo, Novoye Vremya, Birzhevka, Rech, etc. — you will see a multitude of private advertisements, which yield a tremendous income, in fact the principal income, to their capitalist publishers. This is how bourgeois papers hold sway, how they get rich, and how they deal in poison for the people all over the world. In Europe there are newspapers which have a circulation as large as one-third the number of inhabitants of the town (for instance, 12,000 copies in a town with a population of 40,000) and are delivered free to every home, and yet yield their owners a sizable income. These papers live by advertisements paid by private people, while the free delivery of the paper to every home ensures the best circulation of the advertisements.