Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #170988
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: (OT kinda) Newly-discovered TCP flaw |
| Date | 2016-08-11 21:40 +0200 |
| Message-ID | <s53ZE-89S-29@gated-at.bofh.it> (permalink) |
| References | <s50yK-5KE-21@gated-at.bofh.it> <s53df-7wo-3@gated-at.bofh.it> <s53wC-7VY-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thursday 11 August 2016 20:06:26 Gene Heskett wrote: > On Thursday 11 August 2016 15:44:24 Doug wrote: > > On 08/11/2016 12:50 PM, Gene Heskett wrote: > > > On Thursday 11 August 2016 12:47:09 Nicolas George wrote: > > > CC:ing emc-developers, and trinity-users who may not yet be aware of > > > this tcp attack vector thats quite dangerous. And my post to > > > trinity-users was in error, so this corrects it. > > > > > >> Le quintidi 25 thermidor, an CCXXIV, Gene Heskett a écrit : > > >>> to add should be changed to forward slashes: > > >> > > >> You are wrong, sysctl supports both slashes and dots as separators. > > >> > > >> Regards, > > > > > > I changed it back Nicolas, and sysctl -p now returns: > > > root@coyote:/etc/init.d# sysctl -p > > > sysctl: cannot stat /proc/sys//net.ipv4.tcp_challenge_ack_limit: No > > > such file or directory > > > > > > Put the slashes back and I get this: > > > root@coyote:/etc/init.d# sysctl -p > > > .net.ipv4.tcp_challenge_ack_limit = 999999999 > > > > > > Which I assume is the correct response. And yet the echo shows all > > > dots. > > > > > > WTH? Ahh, my bad, no damned biscuit, an extra leading slash snuck > > > in. But if a dot and a slash are the same to sysctl, I should have a > > > file in the wrong place? But I do not. /net is empty. It is in the > > > right place now. And cats the correct value. > > > > > > Sorry about the confusion everybody. > > > > > > Cheers, Gene Heskett > > > > Running PCLOS. I put in the original command with dots. When I run > > sysctl.p from a root environment I get no response, but no error > > either. Don't know the significance of that. > > > > --doug > > Neither do I Doug, sorry. See the announcement on /. today & read the > link to the post from the guys that found it that is in the story, > UCsomething IIRC, see below. A closer read may answer it. > > <https://ucrtoday.ucr.edu/39030> > > And please keep things like this on the list you read it from. A PM is > unfair to the other readers of the list you read it on, so I'll cc the > three lists it was cross posted to as it sounds pretty serious to me. > > And I just noted that the sysctl command you quoted above is incorrect, > its sysctl -p, not sysctl.p. > > Maybe that helps? I copied and pasted the commands exactly, and ran them as root, and got an echo of net.ipv4.tcp_challenge_ack_limit = 999999999 in response to the first and a blank return in response to the second. I don't know the significance. Lisi
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
(OT kinda) Newly-discovered TCP flaw Curt <curty@free.fr> - 2016-08-11 18:00 +0200
Re: (OT kinda) Newly-discovered TCP flaw Reco <recoverym4n@gmail.com> - 2016-08-11 18:30 +0200
Re: (OT kinda) Newly-discovered TCP flaw Curt <curty@free.fr> - 2016-08-11 18:50 +0200
Re: (OT kinda) Newly-discovered TCP flaw Hugo Vanwoerkom <hvw59601@care2.com> - 2016-08-12 23:40 +0200
Re: (OT kinda) Newly-discovered TCP flaw Curt <curty@free.fr> - 2016-08-13 11:10 +0200
Re: (OT kinda) Newly-discovered TCP flaw Reco <recoverym4n@gmail.com> - 2016-08-13 11:20 +0200
Re: (OT kinda) Newly-discovered TCP flaw Curt <curty@free.fr> - 2016-08-13 17:20 +0200
Re: (OT kinda) Newly-discovered TCP flaw Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-08-13 11:20 +0200
Re: (OT kinda) Newly-discovered TCP flaw Curt <curty@free.fr> - 2016-08-13 17:20 +0200
Re: (OT kinda) Newly-discovered TCP flaw Reco <recoverym4n@gmail.com> - 2016-08-13 11:20 +0200
Re: (OT kinda) Newly-discovered TCP flaw Gene Heskett <gheskett@shentel.net> - 2016-08-11 18:40 +0200
Re: (OT kinda) Newly-discovered TCP flaw Gene Heskett <gheskett@shentel.net> - 2016-08-11 19:00 +0200
Re: (OT kinda) Newly-discovered TCP flaw Curt <curty@free.fr> - 2016-08-11 19:30 +0200
Re: (OT kinda) Newly-discovered TCP flaw Dan Ritter <dsr@randomstring.org> - 2016-08-11 19:00 +0200
Re: (OT kinda) Newly-discovered TCP flaw Nicolas George <george@nsup.org> - 2016-08-11 19:10 +0200
Re: (OT kinda) Newly-discovered TCP flaw Gene Heskett <gheskett@shentel.net> - 2016-08-11 20:00 +0200
Re: (OT kinda) Newly-discovered TCP flaw Doug <dmcgarrett@optonline.net> - 2016-08-11 20:50 +0200
Re: (OT kinda) Newly-discovered TCP flaw Gene Heskett <gheskett@shentel.net> - 2016-08-11 21:10 +0200
Re: (OT kinda) Newly-discovered TCP flaw Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-11 21:40 +0200
Re: (OT kinda) Newly-discovered TCP flaw Joe <joe@jretrading.com> - 2016-08-11 22:10 +0200
Re: (OT kinda) Newly-discovered TCP flaw deloptes <deloptes@gmail.com> - 2016-08-11 22:40 +0200
Re: (OT kinda) Newly-discovered TCP flaw Joe <joe@jretrading.com> - 2016-08-11 22:50 +0200
Re: (OT kinda) Newly-discovered TCP flaw deloptes <deloptes@gmail.com> - 2016-08-12 00:00 +0200
Re: (OT kinda) Newly-discovered TCP flaw Bob Weber <bobrweber@gmail.com> - 2016-08-12 00:00 +0200
Re: (OT kinda) Newly-discovered TCP flaw Curt <curty@free.fr> - 2016-08-12 11:00 +0200
Re: (OT kinda) Newly-discovered TCP flaw Gene Heskett <gheskett@shentel.net> - 2016-08-12 12:00 +0200
Re: (OT kinda) Newly-discovered TCP flaw deloptes <deloptes@gmail.com> - 2016-08-12 12:50 +0200
Re: (OT kinda) Newly-discovered TCP flaw Gene Heskett <gheskett@shentel.net> - 2016-08-12 13:30 +0200
Re: (OT kinda) Newly-discovered TCP flaw deloptes <deloptes@gmail.com> - 2016-08-12 22:30 +0200
Re: (OT kinda) Newly-discovered TCP flaw Curt <curty@free.fr> - 2016-08-12 14:30 +0200
Re: (OT kinda) Newly-discovered TCP flaw rhkramer@gmail.com - 2016-08-12 16:50 +0200
Re: (OT kinda) Newly-discovered TCP flaw Greg Wooledge <wooledg@eeg.ccf.org> - 2016-08-12 17:00 +0200
Re: (OT kinda) Newly-discovered TCP flaw Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-08-12 17:20 +0200
Re: (OT kinda) Newly-discovered TCP flaw Greg Wooledge <wooledg@eeg.ccf.org> - 2016-08-12 17:40 +0200
Re: (OT kinda) Newly-discovered TCP flaw rhkramer@gmail.com - 2016-08-12 17:40 +0200
Re: (OT kinda) Newly-discovered TCP flaw "John L. Ries" <jries@salford-systems.com> - 2016-08-12 18:40 +0200
Re: (OT kinda) Newly-discovered TCP flaw Curt <curty@free.fr> - 2016-08-12 18:10 +0200
Re: (OT kinda) Newly-discovered TCP flaw Gene Heskett <gheskett@shentel.net> - 2016-08-12 18:00 +0200
The Debian/Ubuntu/Mint installer was Re: (OT kinda) Newly-discovered TCP flaw Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-13 01:10 +0200
Re: The Debian/Ubuntu/Mint installer was Re: (OT kinda) Newly-discovered TCP flaw Gene Heskett <gheskett@shentel.net> - 2016-08-13 05:20 +0200
Re: The Debian/Ubuntu/Mint installer was Re: (OT kinda) Newly-discovered TCP flaw Lisi Reisz <lisi.reisz@gmail.com> - 2016-08-13 10:50 +0200
Re: (OT kinda) Newly-discovered TCP flaw Gene Heskett <gheskett@shentel.net> - 2016-08-12 05:00 +0200
Re: (OT kinda) Newly-discovered TCP flaw Gene Heskett <gheskett@shentel.net> - 2016-08-12 04:50 +0200
csiph-web