in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment. Deploy Cilium + cilium-etcd-operator Download in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment. Configure the External Etcd When using an external in the kube- controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment. Note Minimum version of kubernetes 1.12 is required

tests Automatically run unit tests on code changes BPF and XDP Reference Guide BPF Architecture Instruction Set Helper Functions Maps Object Pinning Tail Calls BPF to BPF Calls JIT Hardening Offloads Toolchain in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment. Deploy Cilium + cilium-etcd-operator Note First in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment. You will also need an external etcd version 3.1

any more. For example, change instruction JZ to JNZ, so that _pytransform.so can execute even if checking license failed How JIT works? First PyArmor defines an instruction set based on GNU lightning. Then write some core functions by this instruction set in c file, maybe like this: t_instruction protect_set_key_iv = { // function 1 0x80001, 0x50020, ... // function 2 0x80001 0x80001, 0xA0F80, ... } t_instruction protect_decrypt_buffer = { // function 1 0x80021, 0x52029, ... // function 2 0x80001, 0xC0901, ... } Build _pytransform.so, calculate

any more. For example, change instruction JZ to JNZ, so that _pytransform.so can execute even if checking license failed How JIT works? First PyArmor defines an instruction set based on GNU lightning. Then write some core functions by this instruction set in c file, maybe like this: t_instruction protect_set_key_iv = { // function 1 0x80001, 0x50020, ... // function 2 0x80001 0x80001, 0xA0F80, ... } t_instruction protect_decrypt_buffer = { // function 1 0x80021, 0x52029, ... // function 2 0x80001, 0xC0901, ... } Build _pytransform.so, calculate

any more. For example, change instruction JZ to JNZ, so that _pytransform.so can execute even if checking license failed How JIT works? First PyArmor defines an instruction set based on GNU lightning. Then write some core functions by this instruction set in c file, maybe like this: t_instruction protect_set_key_iv = { // function 1 0x80001, 0x50020, ... // function 2 0x80001 0x80001, 0xA0F80, ... } t_instruction protect_decrypt_buffer = { // function 1 0x80021, 0x52029, ... // function 2 0x80001, 0xC0901, ... } Build _pytransform.so, calculate

original byte code changed original byte code: Increase oparg of each absolute jump instruction by the size of wrap header Obfuscate original byte code ... wrap footer: obfuscated scripts in advanced mode won’t work. Because this feature is highly depended on the machine instruction set, it’s only available for x86/x64 arch now. And pyarmor maybe makes mistake if Python interpreter called first time 1. First op is JUMP_ABSOLUTE, it will jump to offset n 2. At offset n, the instruction is to call PyCFunction __armor__. This function will restore those obfuscated bytecode between

original byte code changed original byte code: Increase oparg of each absolute jump instruction by the size of wrap header Obfuscate original byte code ... wrap footer: obfuscated scripts in advanced mode won’t work. Because this feature is highly depended on the machine instruction set, it’s only available for x86/x64 arch now. And pyarmor maybe makes mistake if Python interpreter called first time 1. First op is JUMP_ABSOLUTE, it will jump to offset n 2. At offset n, the instruction is to call PyCFunction __armor__. This function will restore those obfuscated bytecode between

tests Automatically run unit tests on code changes BPF and XDP Reference Guide BPF Architecture Instruction Set Helper Functions Maps Object Pinning Tail Calls BPF to BPF Calls JIT Hardening Offloads Toolchain in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment. Deploy Cilium + cilium-etcd-operator Note First in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment. You will also need an external etcd version 3.1

tests Automatically run unit tests on code changes BPF and XDP Reference Guide BPF Architecture Instruction Set Helper Functions Maps Object Pinning Tail Calls BPF to BPF Calls JIT Hardening Offloads Toolchain in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment. You will also need an external etcd version 3.1 the one that you want, but you have to pick one. Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment and make sure to use Kubernetes >= 1.12. Then, follow

tests Automatically run unit tests on code changes BPF and XDP Reference Guide BPF Architecture Instruction Set Helper Functions Maps Object Pinning Tail Calls BPF to BPF Calls JIT Hardening Offloads Toolchain in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment. Deploy Cilium + cilium-etcd-operator Note First in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare your Kubernetes environment. You will also need an external etcd version 3.1