Plump Orange

Hi, I am a contributor to TCPShield, I happened to do their 2.5 release. With my own digging to find the root cause, I found that infrared cuts off the...

> @xPlumpOrange I hope https://github.com/TCPShield/RealIP/issues/50#issuecomment-846100949 clears things up a bit. Infrared does not manipulate either forwards the payload without modification or creates its own. > > https://github.com/haveachin/infrared/blob/3cbaca23ebb9b2ca3247e2c9787d1b94b3a952d8/protocol/handshaking/serverbound_handshake.go#L84-L99 Thanks for clearing...

> I'm using Infrared reverse proxy. 2.5 broke Infrared since Infrared sends the payload that was correct in 2.4 but is no longer accepted in 2.5 because of the new...

> [haveachin/infrared#71](https://github.com/haveachin/infrared/issues/71) > > This is the issue as marked by Infrared. It points out specific lines of code & errors that I helped to debug (I worked with the...

> Infrared sent the payload without the signature, which worked in 2.4. It seems that in 2.5 it's looking for 4 payload arguments (the original 3 + the signature) and...

> I don't believe the signature argument was present (or required/enforced) in 2.4. It was present, just ignored along with the timestamp verification. The current verification system was used in...

> Infrared doesn't remove the signature. The feature @gcurtiss is talking about upgrades the handshake packet to mimic what TCPShield would send. This enables the preservation of IP addresses like...