Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Administered by:

Server stats:

2.8K
active users

mathstodon.xyz: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#fragmentation

1 post1 participant0 posts today
Replied in thread
Public
Erik van Straten

@Linux : you're definitely not fearmongering.

Eugene Kaspersky warned many times for fragmentation of the internet, like in smh.com.au/technology/cyber-sp more than 11 years ago:
❝
Mr Kaspersky said he feared governments would withdraw to their own parallel networks away from the prying eyes of others, and would cease investing in the development of the public internet, products and services.
❞

(An IMO nice read on internet history: eugene.kaspersky.com/2017/02/0).

Personally I predicted many years ago that online identity fraud would cause too much damage soon.

Fortunately both predictions have not fully materialized, but we're definitely heading in the wrong direction.

Here's one example from many, severly undermining trust in the internet: bleepingcomputer.com/news/secu.

It's not just TLD's: by far most digital certificates are issued by Big Tech with pompous names like "Google Trust Services" - most of them to criminal websites.

See also gist.githubusercontent.com/qbo (src: @_r_netsec in infosec.exchange/@_r_netsec/11).

The Sydney Morning Herald · Cyber spying risks the future of the internet: Eugene KasperskyBy Lia Timson
#Kaspersky#Fragmentation#Impersonation
Public
h o ʍ l e t t

→ Quand fragmentation d’Internet rime avec profits
aoc.media/analyse/2025/02/27/q

« Toute une série d’exemples soulignent comment des acteurs du secteur privé, souvent en raison de leurs modèles #économiques, représentent de véritables défis pour l’unité de l’#Internet, en œuvrant à sa #fragmentation aussi bien au niveau des #infrastructures de l’Internet, que de sa couche #applicative. »

« La prise de conscience de ces #menaces qui pèsent sur l’unité d’Internet peut nous inciter à #agir. »

AOC média · Quand fragmentation d’Internet rime avec profitsBy Lucien CastexFrancesca MusianiClément PerarnaudJulien Rossi
#d
Replied in thread
Public
Ramesh #NotGoingBack

⬆️ @dennyhenke

>> past time, to more specifically redefine my use of computing technology

Agree with your sentiment, but pick your battles unless you want to live like Amish people.

There is life beyond commodity hardware and OS OS. Apps that you need for your job might not be available. Gutted #netNeutrality dooms the open web.

Even federated #socialMedia is doomed to #fragmentation, thanks to cranky, antisocial denizens.

#Mastodon as a last refuge is also lossy ➡️ mastodon.social/@rameshgupta/1

MastodonRamesh #NotGoingBack (@rameshgupta@mastodon.social)⬆️ @GreenFire@mstdn.social >> #Mastodon has been designed for “lossy distribution” "not only loss, but unknowable, invisible loss: you cast a remark out into a network, intending to hail an audience, but some of the potential audience does not see the remark because your part of the network doesn't “see” or talk to their parts. Your remark falling by the wayside for some users is invisible to users who do not see it" #Block by large accounts is also responsible for fragmentation @Gargron @jgkoomey@mastodon.energy @hankg@friendica.myportal.social
Public
Stéphane Bortzmeyer

RFC 9715: IP Fragmentation Avoidance in DNS over UDP

Les requêtes et réponses #DNS peuvent voyager sur divers transports, mais le plus fréquent est UDP. Une réponse de grande taille sur UDP peut dépasser la MTU et donc devoir être fragmentée. La #fragmentation crée divers problèmes et ce RFC décrit les problèmes, et comment éviter la fragmentation.

bortzmeyer.org/9715.html

www.bortzmeyer.orgBlog Stéphane Bortzmeyer: RFC 9715: IP Fragmentation Avoidance in DNS over UDP
Public
Kevin Karhan :verified:

Exactly that is true: #Fragmentation kills the EU!

That's why there's no #AndroidPit #AppCenter anymore!

Thanks again to @dw_innovation / #DWnews for that video.

YouTubeCan Europe survive or thrive in the new world order? | Business BeyondBy DW News
#EUpol#DEpol#USpol
Public
Sami Lehtinen

#btrfs #fragmentation #allocation #filesystem #linux I’m having trouble understanding why these files are allocated like this. And no, this isn’t first nor last time this happens. Note, that these files have NOT been preallocated, NOR these files have been partially updated to cause segments of the file to be updated. Therefore I would assume that delayed allocation would make this file “mostly contiguous” on file system where there is plenty of free space. Note, the pattern repeats throughout the whole file, this is just a very small snippet. The file was written to the disk by Firefox during download from local server.

The primary question is why the file(s) have been written into A,B,A,B,A,B altering “area / location” pattern? - I would appreciate if anyone could give any meaningful answer / guess.

Maybe Firefox flushes files into the disk? - I proved this to be wrong already.

I’ll try to repeat this same test with Python, writing 64 Kibytes blocks at 100 MB/s for 2 gigabytes to see what happens.

Firefox file save from network:

6924:  5118950.. 5120965:   43563352..  43565367:   2016:   36311680: shared
6925:  5120966.. 5120997:   36311680..  36311711:     32:   43565368: shared
6926:  5120998.. 5125061:   43565368..  43569431:   4064:   36311712: shared
6927:  5125062.. 5125093:   36311712..  36311743:     32:   43569432: shared
6928:  5125094.. 5127109:   43569432..  43571447:   2016:   36311744: shared
6929:  5127110.. 5127141:   36311744..  36311775:     32:   43571448: shared
6930:  5127142.. 5138061:   43571448..  43582367:  10920:   36311776: shared
6931:  5138062.. 5138069:   36311776..  36311783:      8:   43582368: shared
6932:  5138070.. 5139389:   43582368..  43583687:   1320:   36311784: shared
6933:  5139390.. 5139413:   36311784..  36311807:     24:   43583688: shared
6934:  5139414.. 5141445:   43583688..  43585719:   2032:   36311808: shared
6935:  5141446.. 5141477:   36311808..  36311839:     32:   43585720: shared
6936:  5141478.. 5143493:   43585720..  43587735:   2016:   36311840: shared
6937:  5143494.. 5143525:   36311840..  36311871:     32:   43587736: shared
6938:  5143526.. 5145541:   43587736..  43589751:   2016:   36311872: shared
6939:  5145542.. 5145573:   36311872..  36311903:     32:   43589752: shared
6940:  5145574.. 5147589:   43589752..  43591767:   2016:   36311904: shared
6941:  5147590.. 5147613:   36311904..  36311927:     24:   43591768: shared
6942:  5147614.. 5148381:   43545016..  43545783:    768:   36311928: shared
6943:  5148382.. 5148389:   36311928..  36311935:      8:   43545784: shared

Python test program:

 642:   478736..  479807:   44152216..  44153287:   1072:   36317921:
 643:   479808..  479823:   36317921..  36317936:     16:   44153288:
 644:   479824..  480911:   44153288..  44154375:   1088:   36317937:
 645:   480912..  480927:   36317937..  36317952:     16:   44154376:
 646:   480928..  481999:   44154376..  44155447:   1072:   36317953:
 647:   482000..  482015:   36317953..  36317968:     16:   44155448:
 648:   482016..  484191:   44155448..  44157623:   2176:   36317969:
 649:   484192..  484207:   36317969..  36317984:     16:   44157624:
 650:   484208..  485295:   44157624..  44158711:   1088:   36317985:
 651:   485296..  485311:   36317985..  36318000:     16:   44158712:
 652:   485312..  486383:   44158712..  44159783:   1072:   36318001:
 653:   486384..  486399:   36318001..  36318016:     16:   44159784:
 654:   486400..  487487:   44159784..  44160871:   1088:   36318017:
 655:   487488..  487503:   36318017..  36318032:     16:   44160872:
 656:   487504..  488575:   44160872..  44161943:   1072:   36318033:
 657:   488576..  488591:   36318033..  36318048:     16:   44161944:
 658:   488592..  489679:   44161944..  44163031:   1088:   36318049:
 659:   489680..  489695:   36318049..  36318064:     16:   44163032:
 660:   489696..  490767:   44163032..  44164103:   1072:   36318065:
 661:   490768..  490783:   36318065..  36318080:     16:   44164104:
 662:   490784..  491871:   44164104..  44165191:   1088:   36318081:
 663:   491872..  491887:   36318081..  36318096:     16:   44165192:
 664:   491888..  492959:   44165192..  44166263:   1072:   36318097:
 665:   492960..  492975:   36318097..  36318112:     16:   44166264:

Most interesting. Answers please!

Replied in thread
Public
Kevin Karhan :verified:

@hon1nbo @foone yeah, but all these things would essentially necessitate a fundamentally incompatible #Fork of the #USB standard, creating #costs, #fragmentation and lessen the likelyhood of success.

  • Not to mention it'll require significant investments in #UserAwareness, #Training and would still have some issues...

I gues a sort-of "Secure HID Port" that mandates proper authentification and does full #E2EE from the Keyboard Matrix / Pointing Device controller up is an option, but you'd have to expect state-sponsored attackers willing to do "Kamikaze" Hacks...

#TLDW: It requires custom silicon and a hard root of trust…

infosec.space/@kkarhan/1137164

YouTubeHow a Mini drill tool defeated security on the Xbox 360 | MVGBy Modern Vintage Gamer
SearchLive feeds
About