512 entries in 0.916s
mircea_popescu: why would you imagine THAT particular aspect of the charade is in so much better shape than all the others ? can'\t fucking compile, right ? why would you be able to
tcp/ip ?
punkman: but there are other tools that can pipe the graphics over
tcp, no?
punkman: why should I want pipe x11 over
tcp?
ascii_field: FUCK this-replaces-x11-but-won't-pipe-over-
tcp assbot: Logged on 26-02-2015 21:09:34; asciilifeform: PeterL: most 'alternatives for x11' dispense with the everything-can-be-piped-over-
tcp trinque: and yet...
tcp 0 0 172.30.0.227:56649 94.125.182.252:7000 ESTABLISHED
mircea_popescu: atm the explanations are, bad
tcp/ip implementation on the machine running it in a very subtle way, or some issue in the firewalls downstream
ascii_field: this drew my attention to the asinine
tcp socket handling in therealbitcoin
trinque: and the qemu commands is... qemu-system-x86_64 -hda root.img -vnc :0 -redir
tcp:2222::22
mircea_popescu: and
tcp with 2nd chan did not catch on precisely because added complexity.
trinque: decimation: I believe /dev/udp and /dev/
tcp are bashisms which do not actually exist as a device node
ascii_field: now we also need a
tcp crud pipe for every access to the blockchain ????!!
decimation: at any rate, the problem isn't udp or
tcp, it's the fact that ip packets route without any signature
jurov: then you'll just enable the reflection attacks right to your
tcp port 80.. indeed fun to watch
mircea_popescu: asciilifeform ftr, i am noit proposing orphan-block
TCP is any better. shouldreally be
TCP/OB
decimation: and it's not exactly like it is hard to game the
tcp state machine
Azelphur: Also, if anything UDP is lighter on the infrastructure than
TCP Azelphur: mircea_popescu: you realise UDP is essential for a number of services and that they wouldn't function using
TCP, right?
punkman: "For
TCP/IP, the tool fingerprints the client-originating SYN packet and the first SYN+ACK response from the server, paying attention to factors such as the ordering of
TCP options, the relation between maximum segment size and window size, the progression of
TCP timestamps, and the state of about a dozen possible implementation quirks (e.g. non-zero values in "must be zero" fields)."
mircea_popescu: asciilifeform the part where they make wildly improbable claims (ex : purely passive traffic fingerprinting mechanisms to identify the players behind any incidental
TCP/IP communications (often as little as a single normal SYN) without interfering in any way.) but then mishmashingly backtrack on it (this release candidate still has a relatively small database of fingerprints) and so on
trinque: in this case it'd be as BingoBoingo said, don't have fucking dumb hosts that can't
TCP BingoBoingo: <trinque> mod6: BingoBoingo: what are your opinions on using random-id and reassemble
tcp in incoming traffic through pf? << Haven't used either of those yet. Pretty much use block, pass, and queue
mod6: im not positive (i don't have access to my pf.conf atm) that i've ever used random-id. i think that's for a very specific problem. but yeah you probably /do/ want scrub all reassemble
tcp trinque: mod6: BingoBoingo: what are your opinions on using random-id and reassemble
tcp in incoming traffic through pf?
mircea_popescu: i dun see how they do anything. either they maintain compliance with
tcp/ip spec as is, in which case they do nothing
ascii_field: 'Trend Micro Threat Intelligence Manager installs a secure web interface (
httpd.exe, tcp port 443/
https) which listens for incoming requests. Several vulnerabilities have been found in the product that would allow a remote attacker to cause the product to execute arbitrary code.'
assbot: Logged on 02-02-2015 23:03:08; mircea_popescu: "I've noticed certain repeating characteristic in the writing of many members of this forum: they construct grammatically correct sentences but absolutely disregard the underlying semantics: incoming vs. outgoing, local vs. remote, source vs. destination, etc. Here in regards to
TCP/IP ports, but I observed that in regards to pretty much any technical issue."
decimation: even microsoft needs a
tcp/ip stack - reminds me of your blog post on 'the burden of supporting all the world'
assbot: Logged on 03-07-2015 01:39:38; asciilifeform: or does it open ordinary sockets and expect a
tcp stack
decimation: it uses a
tcp connection with a special block server I think
ascii_field: there are ~working~
tcp stacks for 'bare bios'
ascii_field: and not, as naive might suppose, the
tcp/ip !
decimation: if you are using a standard linux distro, it's well known that older kernels had buffer bloat/
tcp tuning issues
mircea_popescu: iptables -I INPUT -p
tcp ! -s <permittedIP> -j DROP << is that it ?
mircea_popescu: i am inclined to believe this is more likely the result of original author having nfi how
tcp works rathger than having an idea about some obscure weakness he's deliberately mitigating
assbot: Logged on 06-05-2015 17:21:23; mircea_popescu:
http://log.bitcoin-assets.com/?date=06-05-2015#1122612 << it's actually a fine entry point to explain to anyone why exactly
tcp/ip is so broken. because this IS NOT a trivial task. the price for ipv4 and it's undocumented, buggy, slow and haphazardously ad-hoc nat-routing model is that you can't find out by inspecting yourself. the half-assed, quarter-baked lazy slothful and aol-windowesque implement
trinque: I used /dev/
tcp magic making that gentoo image for mod6 the other day
jurov: williamdunne: it could accept perfectly ordinary
tcp packet
decimation: asciilifeform: why do the sks keyservers take the position that all crypto checks are 'up to the user'? would you expect your router to check ip/
tcp headers?
decimation:
http://www.reed.com/blog-dpr/?page_id=6 < "One project where my friend and officemate Steven T. Kent (now chief scientist and vice president at BBN, and a chief advisor to NSA) and I lost was our strong argument to put mandatory end-to-end encryption into
TCP (and adaptations of the ideas to UDP-based protocols, such as RTP, hich I worked out but abandoned). "
decimation: mircea_popescu: nfs is a method of exporting a filesystem over
tcp mircea_popescu: and this is also a fine entry point for explaining to management noobs the meta point of why exactly a theoretical approach doesn't ever work. yes, you could read the
tcp/ip spec and look for holes. those are the holes in the
tcp/ip spec, not the holes in
tcp/ip.
mircea_popescu:
http://log.bitcoin-assets.com/?date=06-05-2015#1122612 << it's actually a fine entry point to explain to anyone why exactly
tcp/ip is so broken. because this IS NOT a trivial task. the price for ipv4 and it's undocumented, buggy, slow and haphazardously ad-hoc nat-routing model is that you can't find out by inspecting yourself. the half-assed, quarter-baked lazy slothful and aol-windowesque implementation means that yo
☝︎☟︎ assbot: Logged on 29-04-2015 07:33:47; gabriel_laddel: I'll note that I wrote a prototype for the RPC described above - ran into an issue with
TCP or the library I was using it from. Messages were disappearing in flight.
gabriel_laddel: I'll note that I wrote a prototype for the RPC described above - ran into an issue with
TCP or the library I was using it from. Messages were disappearing in flight.
☟︎ ascii_field: 'When we tried wget, it detected errors, retried, and finally succeeded. It said the error was a bad length field in a TLS packet. That didn't make sense at first because we thought TLS packets were error corrected by
TCP.' << incidentally, i am not certain that i agree with the author's conclusion ('reverse heartbleed'.) it may very well be an attempt to exploit other braindamage in
http stack
Chillum: asciilifeform:
tcp/ip layer or application layer?
mircea_popescu: but i wouldn't sign off on him being beaten because
tcp/ip sucks.
Chillum: sockets vs
tcp, should be secure both ways
mod6:
tcp 0 0 0.0.0.0:8333 0.0.0.0:* LISTEN
assbot: Logged on 26-02-2015 21:09:34; asciilifeform: PeterL: most 'alternatives for x11' dispense with the everything-can-be-piped-over-
tcp mircea_popescu: "I've noticed certain repeating characteristic in the writing of many members of this forum: they construct grammatically correct sentences but absolutely disregard the underlying semantics: incoming vs. outgoing, local vs. remote, source vs. destination, etc. Here in regards to
TCP/IP ports, but I observed that in regards to pretty much any technical issue."
☟︎ mircea_popescu: ip addresses seems to be the manner to connect via
tcp/ip neh ?
mats: y'all give
TCP a bad rap. it works exceedingly well for the goals, which is automagical conservative scaling of speed to dynamically changing throughput over opaque paths, which makes it reliable. reliable is good.
Adlai: (this was in a comparison of bitcoin to
tcp/ip or smtp... "you can't short SMTP when your inbox takes forever to load"
mod6: it came back with windows
TCP Socket Errors. I was like ... WTF?! RAGE!