Med-Mastodon

1 post1 participant0 posts today

Max ResingJust wanted to share some thoughts on <a href="https://infosec.exchange/tags/RFC9715" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC9715</a> - an <a href="https://infosec.exchange/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> that defines standards on reducing the <a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> issue of IP fragmentation over <a href="https://infosec.exchange/tags/UDP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UDP</a>. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the <a href="https://infosec.exchange/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Internet</a>. A great leap forward to (hopefully) reduce the reflection/amplification <a href="https://infosec.exchange/tags/DDoS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DDoS</a> potential of DNS.Just today I learned that <a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> will share their public DNS resolvers to limit to ~1400 bytes (smaller adjustments expected while figuring out the sweet spot in production). From now on, DNS responses which exceed this limit will have the truncated flag set instructing the client to resolve back to <a href="https://infosec.exchange/tags/TCP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TCP</a>. <a href="https://infosec.exchange/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv4</a> <a href="https://infosec.exchange/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://infosec.exchange/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ietf</a>

Yvan ーイボん 🗺️ :ferris: :go:<a href="https://hachyderm.io/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv4</a> is hellSo much easier to go <a href="https://hachyderm.io/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> only.

saiki 🚒💨:manjaro: :debian:<a href="https://elbmatsch.de/@DerSchulze" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@DerSchulze</a> Ich nutze auch einen, weil ich hier hinter nem CGNat mit <a href="https://social.tchncs.de/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> stecke und keine IPv4 habe :D aber für gewisse Dinge im Selfhost braucht man leider noch ne <a href="https://social.tchncs.de/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a>.

Публичный пир сетей…Проброс сайта, не имеющего глобального IP-а́дреса, из локальной сети на свой сервер в Интернете (обратный прокси) через сеть Yggdrasil <a href="https://multed.com/2024/04/03/nginx-and-yggdrasill.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://multed.com/2024/04/03/nginx-and-yggdrasill.html</a><a href="https://lor.sh/tags/HTTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTTP</a> <a href="https://lor.sh/tags/%D1%81%D0%B0%D0%B9%D1%82" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#сайт</a> <a href="https://lor.sh/tags/IP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IP</a> <a href="https://lor.sh/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> <a href="https://lor.sh/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> <a href="https://lor.sh/tags/IP_%D0%B0%D0%B4%D1%80%D0%B5%D1%81" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IP_адрес</a> <a href="https://lor.sh/tags/%D1%81%D0%B5%D1%82%D1%8C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#сеть</a> <a href="https://lor.sh/tags/LAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LAN</a> <a href="https://lor.sh/tags/LAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LAN</a> <a href="https://lor.sh/tags/%D1%81%D0%B5%D1%80%D0%B2%D0%B5%D1%80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#сервер</a> <a href="https://lor.sh/tags/VPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPS</a> <a href="https://lor.sh/tags/VDS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VDS</a> <a href="https://lor.sh/tags/%D0%98%D0%BD%D1%82%D0%B5%D1%80%D0%BD%D0%B5%D1%82" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Интернет</a> <a href="https://lor.sh/tags/Yggdrasil" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Yggdrasil</a> <a href="https://lor.sh/tags/nginx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nginx</a> <a href="https://lor.sh/tags/proxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proxy</a> <a href="https://lor.sh/tags/reverseproxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reverseproxy</a> <a href="https://lor.sh/tags/reverse_proxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reverse_proxy</a> <a href="https://lor.sh/tags/publicpeer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#publicpeer</a> <a href="https://lor.sh/tags/%D1%81%D0%B8%D1%81%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#сисадмин</a> <a href="https://lor.sh/tags/%D0%BB%D0%B0%D0%B9%D1%84%D1%85%D0%B0%D0%BA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#лайфхак</a> <a href="https://lor.sh/tags/readme" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#readme</a>

asmwToday, when looking into <a href="https://infosec.exchange/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv4</a>/#ipv6 issues, I learned about <a href="https://infosec.exchange/tags/happyeyeballs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#happyeyeballs</a> (<a href="https://en.wikipedia.org/wiki/Happy_Eyeballs" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/Happy_Eyeballs</a>).Such a pretty name for such an annoying problem.

MichaelQuestion to the network people out there:Are there any ISPs that are IPv6 only (without providing a NAT/whatever)?Background: Having an argument with a provider that hasn't published any AAAA records, and whilst I think that's poor form, I'm wondering if this would actually negatively affect any actual users in practice?<a href="https://mstdn.thms.uk/tags/ip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ip</a> <a href="https://mstdn.thms.uk/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://mstdn.thms.uk/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv4</a> <a href="https://mstdn.thms.uk/tags/isp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#isp</a>

Kevin Karhan :verified:<a href="https://mastodon.ie/@DoctorBrodsky" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@DoctorBrodsky</a> <a href="https://toot.wales/@woe2you" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@woe2you</a> <a href="https://hachyderm.io/@miah" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@miah</a> given <a href="https://infosec.space/tags/Quad9" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Quad9</a> bowed before the <a href="https://infosec.space/tags/Contentmafia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Contentmafia</a> and censored <a href="https://infosec.space/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> requests, I'll continue to recommend using <a href="https://infosec.space/tags/OpenNIC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenNIC</a>'s Servers <a href="https://github.com/greyhat-academy/lists.d/blob/a4a7ccf70d8504ebbffd7e5fbcd5630294860434/dns.servers.list.tsv" rel="nofollow noopener noreferrer" target="_blank">instead</a><code>94.103.153.176 & 2a02:990:219:1:ba:1337:cafe:3</code> as well as <code>144.76.103.143 & 2a01:4f8:192:43a5::2</code> <ul><li>If you <a href="https://mastodon.ie/@DoctorBrodsky/114251891439728473" rel="nofollow noopener noreferrer" target="_blank">only add a single</a> <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> address, no <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> resolution will take place over said provider or worse even no IPv6 connectivity at all...</li></ul>I merely <a href="https://github.com/greyhat-academy/lists.d/blob/a4a7ccf70d8504ebbffd7e5fbcd5630294860434/dns.servers.list.tsv#L25" rel="nofollow noopener noreferrer" target="_blank">retain quad9</a> on said list for archival purposes. I Yeeted <a href="https://infosec.space/tags/CloudFlare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudFlare</a> aka. <a href="https://infosec.space/tags/ClownFlare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ClownFlare</a> since they are a <a href="https://infosec.space/tags/RogueISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RogueISP</a>!

Kevin Karhan :verified:<a href="https://mastodon.neilzone.co.uk/@neil" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@neil</a> my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ISP</a> is <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4only</a> and refuses to allocate me even a single /64 of <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> but happily offers me another /28 of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a>'s...<ul><li>I wish I was kidding…</li></ul>

Quincy<a href="https://chaos.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a>-Adressen als Wertanlage

Kevin Karhan :verified:<a href="https://awawa.meo.ws/@fusl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fusl</a> <a href="https://mastodon.online/@mnalis" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mnalis</a> <a href="https://infosec.exchange/@0xF21D" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@0xF21D</a> I do that with <a href="https://infosec.space/tags/pfSense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pfSense</a> & <a href="https://infosec.space/tags/OPNsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OPNsense</a> (depending on the exact network in question) and have it merge <a href="https://github.com/greyhat-academy/lists.d/blob/main/dns.servers.list.tsv" rel="nofollow noopener noreferrer" target="_blank">multiple sources</a> that get cached.In total, I do may out the 30 DNS servers and whilst I have <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4only</a>, I have everything ready for <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DualStack</a> (<a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> + <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>) once my ISP stops keeing it's thumbs um their ass...<a href="https://infosec.space/tags/sarcasm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sarcasm</a>

Kevin Karhan :verified:<a href="https://digitalcourage.social/@krzym" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@krzym</a> <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fuchsiii</a> <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BNetzA</a> und wie <a href="https://infosec.space/tags/Diesel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Diesel</a> funktioniert <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a>...<a href="https://www.youtube.com/watch?v=myXi1KMyClc" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=myXi1KMyClc</a><a href="https://infosec.space/tags/Sarkasmus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sarkasmus</a>

Kevin Karhan :verified:<a href="https://digitalcourage.social/@krzym" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@krzym</a> <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fuchsiii</a> solange <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BNetzA</a> nicht mindestens ein /64 an <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> pro <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> vorschreibt wird sich nix dran ändern.<ul><li>Erst wenn <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DualStack</a> flächendeckend ist kann IPv4 abgeschaltet werden!</li></ul>

Dan OachsNo way I can properly explain this in 500 characters, but the short version is this:Don't use a shared IP address for your website/app and expect zero issues.If your cloud hosted app/website happens to share an IP address with another app that scans the entire internet, don't be surprised if your app/website gets blocked and your customers can't reach you. :(In this case, that IP address is 199.36.158.199. Take a look at the SSL cert for all the domains hosted there. <a href="https://ipv6.social/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a> <a href="https://ipv6.social/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv4</a>

Radio AzureusTIL about lsd(1)What an awsome addition to my lolcat arsenal!The acronym is not correctly used by me in this case, because I **know** I used LSD in the 1990's (the command in a UNIX ENV:) and LSD is just as pretty as it was psychedelic in the last century!`man lsd `An ls command with a lot of pretty colors and some other stuff.<a href="https://fuzzies.wtf/@altbot" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@altbot</a> 🖋️ <a href="https://mastodon.social/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bash</a> <a href="https://mastodon.social/tags/sh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sh</a> <a href="https://mastodon.social/tags/zsh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zsh</a> <a href="https://mastodon.social/tags/ksh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ksh</a> <a href="https://mastodon.social/tags/csh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#csh</a> <a href="https://mastodon.social/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Networking</a> <a href="https://mastodon.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> <a href="https://mastodon.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> <a href="https://mastodon.social/tags/ProxMox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProxMox</a> <a href="https://mastodon.social/tags/freeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freeBSD</a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#POSIX</a> <a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Programming</a>

LavX NewsIPv4 Addresses Now Serve as Collateral for $100M Loans: A New Era in Networking FinanceIPv4.Global has launched a revolutionary loan service that allows companies to use their IPv4 addresses as collateral, a move that could reshape the financial landscape for network operators. With IPv...<a href="https://news.lavx.hu/article/ipv4-addresses-now-serve-as-collateral-for-100m-loans-a-new-era-in-networking-finance" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/ipv4-addresses-now-serve-as-collateral-for-100m-loans-a-new-era-in-networking-finance</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/CloudComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudComputing</a> <a href="https://mastodon.cloud/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> <a href="https://mastodon.cloud/tags/NetworkingFinance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetworkingFinance</a>

mansi18IPv4 Addresses & Subnetting: Your Ultimate GuideJoin CISSP training - <a href="https://infosectrain.com/courses/cissp-certification-training/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://infosectrain.com/courses/cissp-certification-training/</a><a href="https://mastodon.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> <a href="https://mastodon.social/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Networking</a> <a href="https://mastodon.social/tags/Subnetting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Subnetting</a> <a href="https://mastodon.social/tags/CIDR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CIDR</a> <a href="https://mastodon.social/tags/PrivateIP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PrivateIP</a> <a href="https://mastodon.social/tags/DataNetworking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DataNetworking</a>

Kevin Karhan :verified:Right now the problem with <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> <a href="https://infosec.space/tags/BridgeDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BridgeDB</a> is that I can't get <a href="https://infosec.space/tags/webtunnel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webtunnel</a> bridges on <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> even when I try to specify those by setting <code>ipv6=no</code> at the URL:<a href="https://bridges.torproject.org/bridges?transport=webtunnel&ipv6=no" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bridges.torproject.org/bridges?transport=webtunnel&ipv6=no</a>And no, removing IPv6 from the URL doesn't yield any IPv4 results either. <a href="https://bridges.torproject.org/bridges?transport=webtunnel" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bridges.torproject.org/bridges?transport=webtunnel</a>It would be better if <a href="https://infosec.space/tags/BridgeDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BridgeDB</a> would have a radio button / switch to choose IPv4 & <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> for this reason.

Kevin Karhan :verified:<a href="https://infosec.space/tags/WhatsMissing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WhatsMissing</a>: A tool to check if <a href="https://infosec.space/tags/TorBridges" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TorBridges</a> are still available/online/reachable that one can use either <a href="https://infosec.space/tags/standalone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#standalone</a> (with <a href="https://infosec.space/tags/TorBrowser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TorBrowser</a> and/or <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tor</a> Expert Bundle) or on <a href="https://venera.social/profile/tails_live" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tails_live</a> / <a href="https://fosstodon.org/@tails" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tails</a> / <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tails</a>. <ul><li>Cuz I do run into issues and kinda want to sort <a href="https://infosec.space/tags/Bridges" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bridges</a> by availability so I don't waste time on a <a href="https://infosec.space/tags/TorBridge" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TorBridge</a> that is down and also thin-out the list of bridges that ain't online anymore.</li></ul>Whilst I do acknowledge that <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> do disrecommend having a huge list of Tor Bridges on hand, I do regularly need them for contacts who are behind a <a href="https://infosec.space/tags/GreatFirewall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GreatFirewall</a> and can't <a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSH</a>-Tunnel out of it.<ul><li>Sadly <a href="https://infosec.space/tags/BridgeDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BridgeDB</a> <a href="https://bridges.torproject.org" rel="nofollow noopener noreferrer" target="_blank">doesn't offer</a> good <a href="https://infosec.space/tags/filtering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filtering</a> options so one can't just query types effectively like "I need <a href="https://infosec.space/tags/webtunnel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webtunnel</a> on <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a>" or "I can only use Ports 80 & 443 on <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>" which may work.</li></ul>Espechally being able to filter for <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4only</a> and not just <a href="https://infosec.space/tags/IPv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6only</a> is something I miss, alongside the filter for <a href="https://infosec.space/tags/PluggableTransports" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PluggableTransports</a> type as <a href="https://social.librem.one/@guardianproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@guardianproject</a> <a href="https://infosec.space/tags/Orbot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Orbot</a> seems to only handle <a href="https://infosec.space/tags/obfs4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#obfs4</a> and not webtunnel or <a href="https://infosec.space/tags/meek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#meek</a> at all...<ul><li>I'm pretty certain that merely pinging a bridge at it's port isn't working as a shure-fire way to check for it's availability.</li></ul>

SkorpySo we waited 505 days to get our /24 <a href="https://chaos.social/tags/IPvLegacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPvLegacy</a> today. This is just crazy madness, <a href="https://chaos.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> must die.<a href="https://chaos.social/tags/IP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IP</a> <a href="https://chaos.social/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a> <a href="https://chaos.social/tags/RIPE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RIPE</a> <a href="https://chaos.social/tags/Freifunk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Freifunk</a>

Kernel Comments/* Funny. This algorithm seems to be very broken. These formulae increase RTO, when it should be decreased, increase too slowly, when it should be increased quickly, decrease too quickly etc. I guess in BSD RTO takes ONE value, so that it is absolutely does not matter how to _calculate_ it. Seems, it was trap that VJ failed to avoid. 8) */<a href="https://elixir.bootlin.com/linux/v6.13.3/source/net/ipv4/tcp_input.c#L884-L889" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://elixir.bootlin.com/linux/v6.13.3/source/net/ipv4/tcp_input.c#L884-L889</a><a href="https://infosec.exchange/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://infosec.exchange/tags/kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kernel</a> <a href="https://infosec.exchange/tags/net" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#net</a> <a href="https://infosec.exchange/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv4</a>

Recent searches

Search options

Administered by:

Server stats:

#ipv4