Search
150 results for “jschauma”
-
@jschauma Not sure why I got banned, I just pointed out in the ticket system they forgot to capitalize the ‘c’ in CURL.
-
Far from the only problem with atopgpud.
-
@jschauma
I just cancelled my WaPo subscription. -
@jschauma Thank you for your insightful talk on the distribution of #IPv4 at #RIPE88. If you missed the talk (and you should really watch this one), you can read about Jan's research on #ripelabs
🔗https://labs.ripe.net/author/jschauma/whose-cidr-is-it-anyway/ -
Seems like a similar balance in proportion. The second (time in general) is not formally metric.
We have a base 10 hindu-arabic number system from a series of historical chances, not by design or competition. A base 12 sys would arguably be better in most, if not every way (for example).
Also, it might have been better to wait until we have working (explanatory) theories that do not contradict each other to finalize some of these standards because the errors are now embedded into the system & prevent alternative models from even being considered (for egos & profit margins, etc).
-
@jschauma
A good thing then that Guix implemented the full source Bootstrap.Also @nixos_org is now prototyping and implementing the full source Bootstrap right now, thanks to @emilyposting.
Let's just hope that other distributions may wake up and follow soon.
-
-
@yrlf @jschauma Reproducible Builds don't help here, you can be reproducibly malicious. What you need is a bit stronger, i.e. #BootstrappableBuilds. If you build the world starting from a tiny sub 1KiB binary, you can prove that there is no self replicating backdoor coming from software. You could still have one from lower levels, e.g. hardware. Those are both significantly harder to implement but also hard to solve.
-
@janneke @jschauma @nixos_org @emilyposting Also Freedesktop SDK (with the exception of rust) uses #bootstrappableBuilds.
-
@markd @becomingwisest @jschauma I need to get this article republished on how to self-service enable #IPv6 on existing #Akamai configurations:
https://web.archive.org/web/20220913213213/https://developer.akamai.com/blog/2020/05/04/enable-ipv6-your-edge-hostnames -
@markd @becomingwisest @jschauma #Akamai has made #IPv6 dualstack the default for around a decade for new customer configurations. I talk some about why customers don't dual-stack (and why they should!) in https://www.akamai.com/blog/trends/10-years-since-world-ipv6-launch
Many customer sites have been on long enough to pre-date the switch of the default, but we do still see some rate of opting out. Some top reasons include:
* Operationally conservative and lack of understanding of the value ("if it isn't broke don't fix it" or "seems safer"), or have trouble justifying the effort to make the change safely with testing.
* Lack of support in their log processing and/or header processing and/or advanced business logic for IP handling. For example, companies may be using a third-party anti-fraud product which doesn't support IPv6. With Akamai's large base of Enterprise customers this is frustratingly common and the "just hash the IPv6 to an IPv4" makes things worse rather than helping.
* Auth tokens bound to IP addresses. (eg, setting it via IPv4 and validating via IPv6 fails, or vice-versa -- see https://www.akamai.com/blog/developers/why-you-shouldn-t-tie-ip-addresses-to-tokens )
* Custom or uncommon clients which break in the presence of IPv6. This is rare but I've seen it, for example some local streaming provider may have a user base with old Smart TVs that interact poorly with some ISP's somewhat broken IPv6 setup. I hear this less now, but it used to be common even a few years ago.Note that it's worth checking both the "www" and apex name version of some of these, as in some cases the apex example.com name is IPv4-only but redirects to a dualstack "www" name due to CNAME-at-the-apex limitations.
-
@the_roamer @jschauma
I was really disappointed by this article. It isn't exactly news since this has been happening globally for over a year now. And the analysis was superficial, not looking at wider economic and political factors making the ideal of the university challenging to sustain in a totally f**ked world. Whole thing stank of American exceptionalism and needed a bit of basic research outside the author's personal experience. So speaks #Reviewer2 -
@kkarhan @landley @jschauma @ryanc @0xabad1dea "still, a #64bit #AddresaSpace would've been more than sufficient". Yes, the famous "640KB should be enough for everyone". "A #128bit address space is quite inefficient" Why/where/how inefficient? Do DFZ routers have problems? Is storage SO constrained nowadays that we can't store 128bits values? Or is this again the revenge of "oh my god IPv6 is so difficult, I can't remember all those long addresses like I did in IPv4"?
-
distrib/utils/embedded/files: ec2_init
jschauma: Improve metadata fetching to work more reliably across
IPv4-only, IPv6-only, and dual-stack instances.http://cvsweb.netbsd.org/bsdweb.cgi/src/distrib/utils/embedded/files/ec2_init.diff?r1=1.7&r2=1.8
-
Lien recensant l'ensemble des #correctifs pour les #distributions #Linux contre #CopyFail :
https://mstdn.social/@jschauma/116505274281284939
#CopyFail #Patch #Update #Vulnerability #Security #Cybersecurity #Ubuntu #Debian #Fedora #Suse #RedHat #Alpine #AlmaLinux #Trixie #Root #Kernel #Docker #Kubernetes #PrivilegeEscalation #Privilege #UserPrivilege
-
Lien recensant l'ensemble des #correctifs pour les #distributions #Linux contre #CopyFail :
https://mstdn.social/@jschauma/116505274281284939
#CopyFail #Patch #Update #Vulnerability #Security #Cybersecurity #Ubuntu #Debian #Fedora #Suse #RedHat #Alpine #AlmaLinux #Trixie #Root #Kernel #Docker #Kubernetes #PrivilegeEscalation #Privilege #UserPrivilege
-
Lien recensant l'ensemble des #correctifs pour les #distributions #Linux contre #CopyFail :
https://mstdn.social/@jschauma/116505274281284939
#CopyFail #Patch #Update #Vulnerability #Security #Cybersecurity #Ubuntu #Debian #Fedora #Suse #RedHat #Alpine #AlmaLinux #Trixie #Root #Kernel #Docker #Kubernetes #PrivilegeEscalation #Privilege #UserPrivilege
-
Lien recensant l'ensemble des #correctifs pour les #distributions #Linux contre #CopyFail :
https://mstdn.social/@jschauma/116505274281284939
#CopyFail #Patch #Update #Vulnerability #Security #Cybersecurity #Ubuntu #Debian #Fedora #Suse #RedHat #Alpine #AlmaLinux #Trixie #Root #Kernel #Docker #Kubernetes #PrivilegeEscalation #Privilege #UserPrivilege
-
Kickoff the weekend with our latest episode of #BreakingBadness as we discuss @jschauma’s research on who controls the Internet. Here's a clip from @seanmcnee on why it's important to the future of DNS and the growth of the Internet. Listen to the full episode here:
https://www.domaintools.com/resources/podcasts/141-scam-a-lama-ding-dong?utm_source=Social&utm_medium=Mastodon&utm_campaign=Breaking-Badness -
There is a great summary of the state of HTTPS RRs (#SVCB style records) at https://netmeister.org/blog/https-rrs.html
Thanks @jschauma for writing this – it also explains in its footnotes why Chromium so far fails my https://svcbtest.amsuess.com/ test site – it doesn't allow setting a different target name. -
There is a great summary of the state of HTTPS RRs (#SVCB style records) at https://netmeister.org/blog/https-rrs.html
Thanks @jschauma for writing this – it also explains in its footnotes why Chromium so far fails my https://svcbtest.amsuess.com/ test site – it doesn't allow setting a different target name. -
There is a great summary of the state of HTTPS RRs (#SVCB style records) at https://netmeister.org/blog/https-rrs.html
Thanks @jschauma for writing this – it also explains in its footnotes why Chromium so far fails my https://svcbtest.amsuess.com/ test site – it doesn't allow setting a different target name.
