GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:21:40 JST kajer kajer
    • cR0w :cascadia:
    • Ryan Castellucci :nonbinary_flag:

    @cR0w @ryanc I'll need a cert that covers FD8C::/8 if these people fuckers I work with have anything to say about it... If I give them 1, they will want all 16 trillion 1,329,227,995,784,915,872,903,807,060,280,344,576.

    Maybe there is a way to fuck with how certs are parsed like using [FD8C::/8] as a DNS name?

    I don't know. That ticket will probably sit in my queue until the day I quit, and many years thereafter.

    In conversation about 2 months ago from gnusocial.jp permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:02:11 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @cR0w @kajer what manner of fuckery is it that you desire, my friends?

      In conversation about 2 months ago permalink
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:02:12 JST kajer kajer
      in reply to
      • cR0w :cascadia:
      • Ryan Castellucci :nonbinary_flag:

      @cR0w I'm tempted to call on @ryanc to do stupid certificate things just for fun

      In conversation about 2 months ago permalink
    • Embed this notice
      cR0w :cascadia: (cr0w@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:02:12 JST cR0w :cascadia: cR0w :cascadia:
      in reply to
      • Ryan Castellucci :nonbinary_flag:

      @kajer @ryanc Yes! I'll get the popcorn.

      In conversation about 2 months ago permalink
    • Embed this notice
      cR0w :cascadia: (cr0w@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:02:13 JST cR0w :cascadia: cR0w :cascadia:
      in reply to

      @kajer If you're handing out certs like that, where can I put in my requests? 😈

      In conversation about 2 months ago permalink
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:02:13 JST kajer kajer
      in reply to
      • cR0w :cascadia:

      @cR0w do wildcard certs apply to 192.168/16 address too? How about a wildcard for 10/8 ?

      sign me up!

      In conversation about 2 months ago permalink
    • Embed this notice
      cR0w :cascadia: (cr0w@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:02:13 JST cR0w :cascadia: cR0w :cascadia:
      in reply to

      @kajer Yes please! I'd also like some 169.254.0.0/16 if you've got them.

      In conversation about 2 months ago permalink
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:02:14 JST kajer kajer

      today's first ticket:

      We need this RFC4193 IPv6 address to use a certificate from the company's openssl CA

      You want openssl to give us a trusted cert for a non-routed IPv6 address?!

      lol, what a week

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:06:06 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @cR0w @kajer FWIW I already have tooling that can generate certs for private address space from an internal CA because of course I do.

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:21:40 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w It turns out that no, there is no such thing as an IP wildcard certificate, much to my surprise.

      Closest you can get is an intermediate CA with name constraints and then they can mint their own per-ip certificates.

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:22:28 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w you can stuff individual IPv6 addresses in the subject alternative name field though

      In conversation about 2 months ago permalink
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:24:45 JST kajer kajer
      in reply to
      • cR0w :cascadia:
      • Ryan Castellucci :nonbinary_flag:

      @ryanc @cR0w I have seen blursed certs with entire /24s for IPv4 stuffed in the subj-alt names... I just dont want to do this... for v4 or v6

      fucking use DNS for your shit

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:28:32 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w find me an example of such a certificate and I will figure out how to replicate it

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:30:16 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w

      Here's what I found:
      https://security.stackexchange.com/questions/91368/ip-range-in-ssl-subject-alternative-name

      In conversation about 2 months ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: cdn.sstatic.net
        IP range in SSL subject alternative name
        Is it possible to create a SSL (self-signed) certificate by specifying IP range in the SAN section of OpenSSL conf like this? IP.1=192.168.0.0/24
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:31:15 JST kajer kajer
      in reply to
      • cR0w :cascadia:
      • Ryan Castellucci :nonbinary_flag:

      @ryanc @cR0w I found the same thing. I refuse out of principal. I know I work at a startup and a level of jank is involved... But damn.

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:32:25 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w I'd probably have to read the boringssl source code to see whether chrome will handle it...

      In conversation about 2 months ago permalink
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:32:53 JST kajer kajer
      in reply to
      • cR0w :cascadia:
      • Ryan Castellucci :nonbinary_flag:

      @ryanc @cR0w lol @ryanc reading dcoumentation smells like a CVE in the pipeline

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:35:49 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w I'm pretty sure they started fuzzing their certificate validation code paths after a few rounds of researchers setting it on fire

      In conversation about 2 months ago permalink
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:38:33 JST kajer kajer
      in reply to
      • cR0w :cascadia:
      • Ryan Castellucci :nonbinary_flag:

      @ryanc @cR0w oh thats right... chrome, owning the majority browser market, gets to do what they want regardless of rules because what are you going to do about it?

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:41:21 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w I just spoke with someone from let's encrypt who has looked at the relevant code in a number of implementations and they confirm CIDR ranges aren't honored in SANs.

      If I had an exploit which would allow this, I would now be dropping it because it would be funny, but alas...

      In conversation about 2 months ago permalink
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:45:56 JST kajer kajer
      in reply to
      • cR0w :cascadia:
      • Ryan Castellucci :nonbinary_flag:

      @ryanc @cR0w I am tempted attempt a shellshock to get this... But certificate parsing is probably secure enough to prevent this... right? RIGHT?

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:47:25 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w

      This has an example of generating a SAN with an ipv4 address, IPv6 should work...

      https://github.com/ryancdotorg/certpy

      In conversation about 2 months ago permalink
    • Embed this notice
      Fritz Adalis (fritzadalis@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:52:51 JST Fritz Adalis Fritz Adalis
      in reply to
      • cR0w :cascadia:
      • Ryan Castellucci :nonbinary_flag:

      @ryanc @cR0w @kajer
      Pretty sure Microsoft's CA does this out of the box. This is why Microsoft always gets the best quadrant.

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:54:09 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w as I said, fuzz testing...

      Now, if you wanted to break GnuTLS, that's probably still got some fun things in the dumpster between the fire.

      In conversation about 2 months ago permalink
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:57:56 JST kajer kajer
      in reply to
      • cR0w :cascadia:
      • Ryan Castellucci :nonbinary_flag:

      @ryanc @cR0w i am not going to be enabling this request by giving them a trusted cert for an ipaddress. I doubt our CA will do it, but I'm not going to ask. They don't want any type of DNS, just the internal use IP.

      Hi Digicert, can I get a trusted cert for 192.168.1.1 please?

      Hi Digicert, can I get a trusted cert for 2001:db8::1 please?

      In conversation about 2 months ago permalink
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:59:04 JST kajer kajer
      in reply to
      • cR0w :cascadia:
      • Ryan Castellucci :nonbinary_flag:

      @ryanc @cR0w LOL I just re-read the ticket...

      ALL servers at ALL sites will use the SAME IPv6 address, so they only need the ONE certificate.

      W T A F

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 03:59:04 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w just make the certificate with some fun text embedded in the PEM

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 04:20:55 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w DigiCert isn't going to oblige, so they run your internal CA?

      In conversation about 2 months ago permalink
    • Embed this notice
      kajer (kajer@infosec.exchange)'s status on Thursday, 20-Mar-2025 04:24:46 JST kajer kajer
      in reply to
      • cR0w :cascadia:
      • Ryan Castellucci :nonbinary_flag:

      @ryanc @cR0w the wording of the ticket broke my brain. they want a trusted ca to give us a cert for their one ipv6 address they intend to reuse at multiple sites.

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 04:36:12 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w oh, lol, that's not bloody happening

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 04:37:10 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w they can set a public DNS name to an internal IP, but you know that...

      In conversation about 2 months ago permalink
    • Embed this notice
      Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Thursday, 20-Mar-2025 17:01:45 JST Ryan Castellucci :nonbinary_flag: Ryan Castellucci :nonbinary_flag:
      in reply to
      • cR0w :cascadia:

      @kajer @cR0w statements of the utterly deranged?

      In conversation about 2 months ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.