CensoredUsername
commented
3 years ago currently offering bytecode.rpyb as well, which is unaffected by rpyc header spoofing. Turns out that you could literally just rename the old un.rpyc to bytecode.rpyb as well and put it there to have it work but in the interest of future compatibility I've made some slight changes.
rpyc header spoofing and other shenanigans break un.rpyc. We could instead try injecting as a the bytecode storage file. These are also just pickles (and just cache data so it's not a problem if they're replaced, they will be regenerated. As soon as the unpickling machinery has read their version info we've already done our thing.