Brutkey

da_667
@da_667@infosec.exchange

I really wish you all weren't so cocksure about letting shit like HTTP/1.1 die.

Gonna miss the last vestige of the web that doesn't require wireshark to fuckin' parse it.

I kinda hate that HTTP/2 is straight binary and requires wireshark to make any sense of it, and that http/3 is basically just quic, which is google's love child of weird shit.

1.3.6.1.4.1.61513
@xssfox@cloudisland.nz

@da_667@infosec.exchange yeah... I feel like suggesting http2 is a safer alternative is probably misguided and bias'd. It'll just have different problems.

da_667
@da_667@infosec.exchange

@xssfox@cloudisland.nz

looks at shit like ysoserial and ysoserial.net

1.3.6.1.4.1.61513
@xssfox@cloudisland.nz

@da_667@infosec.exchange load balancer were a mistake

AndThisIsMrsPeacock 🏳‍🌈
@andthisismrspeacock@mas.to

@xssfox@cloudisland.nz @da_667@infosec.exchange The number of times I get requests from dev that are like "uhh, can you just add this 500 line iRule to make the F5s rewrite the traffic stream to fix [problem we created via shitty code]" and like, no. NO. NO. BAD DEVELOPER. [bops on nose with rolled up newspaper]

AndThisIsMrsPeacock 🏳‍🌈
@andthisismrspeacock@mas.to

@xssfox@cloudisland.nz @da_667@infosec.exchange The number of times I get requests from dev that are like "uhh, can you just add this 500 line iRule to make the F5s rewrite the traffic stream to fix [problem we created via shitty code]" and like, no. NO. NO. BAD DEVELOPER. [bops on nose with rolled up newspaper]

1.3.6.1.4.1.61513
@xssfox@cloudisland.nz

@andthisismrspeacock@mas.to @da_667@infosec.exchange I've always held the opinion that teams should have build and deploy processes so slick that it's easier to fix/patch the issue than reach for the waf

1.3.6.1.4.1.61513
@xssfox@cloudisland.nz

@andthisismrspeacock@mas.to @da_667@infosec.exchange I've always held the opinion that teams should have build and deploy processes so slick that it's easier to fix/patch the issue than reach for the waf