• 4 Posts
  • 441 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2023

help-circle

  • It’s not immediately a DNS issue. Usually if there’s no response within less then a second, then a browser will skip IPv6 and use IPv4 (Happy Eyeballs). But in this case the server responds with an SSL error over IPv6.

    curl -v -6 "https://rebeltechalliance.org/"
    * Host rebeltechalliance.org:443 was resolved.
    * IPv6: 2a10:e000:1::10
    * IPv4: (none)
    *   Trying [2a10:e000:1::10]:443...
    * ALPN: curl offers h2,http/1.1
    * TLSv1.3 (OUT), TLS handshake, Client hello (1):
    *  CAfile: /data/data/com.termux/files/usr/etc/tls/cert.pem
    *  CApath: /data/data/com.termux/files/usr/etc/tls/certs
    * TLSv1.3 (IN), TLS handshake, Server hello (2):
    * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    * TLSv1.3 (OUT), TLS handshake, Client hello (1):
    * TLSv1.3 (IN), TLS handshake, Server hello (2):
    * TLS connect error: error:00000000:lib(0)::reason(0)
    * OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to rebeltechalliance.org:443
    * closing connection #0
    curl: (35) TLS connect error: error:00000000:lib(0)::reason(0)
    






  • I never mentioned vulnerabilities, I just wanted to point out that, RDP doesn’t really work without a graphical session, Windows Server Core gets around this by being a graphical session (although very basic).

    Also I’m not sure, but I don’t think Windows handles RDP on the kernel level, it’s just nicely tied in with DWM and doesn’t have to deal with the multitude of window managers on Linux.

    Handling RDP on the kernel level does sound like a bad idea security wise, but there should be a better way.










  • Unless you are moving gigabits of data, you won’t notice the difference the smaller header payload of ipv6 offers.

    IPv6 headers are usually bigger anyway1, so the only advantage is more efficient routing (so infinitesimally better latency), but in my experience most routers only support IPv4 hw offload and not IPv6, so it’s only more efficient in theory.

    I just like IPv6 because I get a whole /56 prefix to play with, and devices often randomise their host portion through the privacy extensions, meaning they use a new address each day or so.

    1 IPv4 is usually ~20 bytes, but it can be up to 60 bytes if you stack a lot of options, IPv6 is only 40 bytes AFAIK.