issue for build windows imps

[BabelQwerty]

cargo rustc --lib --release -- -C relocation-model=pic

error: environment variable `UUID` not defined at compile time
  --> src\proto.rs:94:18
   |
94 |         session: env!("UUID").to_string(), //ignore error in vs code, env is set
   |                  ^^^^^^^^^^^^
   |
   = help: use `std::env::var("UUID")` to read the variable at run time
   = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: environment variable `SLEEP` not defined at compile time
   --> src\proto.rs:102:16
    |
102 |         sleep: env!("SLEEP").to_string(), //ignore error in vs code, env is set
    |                ^^^^^^^^^^^^^
    |
    = help: use `std::env::var("SLEEP")` to read the variable at run time
    = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: environment variable `JITTER` not defined at compile time
   --> src\proto.rs:450:34
    |
450 |                 let mut jitter = env!("JITTER").to_string(); //ignore error in vs code, env is set
    |                                  ^^^^^^^^^^^^^^
    |
    = help: use `std::env::var("JITTER")` to read the variable at run time
    = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: environment variable `SERVER` not defined at compile time
   --> src\proto.rs:459:35
    |
459 |                 let server_name = env!("SERVER").to_string(); //ignore error in vs code, env is set
    |                                   ^^^^^^^^^^^^^^
    |
    = help: use `std::env::var("SERVER")` to read the variable at run time
    = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: environment variable `PORT` not defined at compile time
   --> src\proto.rs:460:28
    |
460 |                 let port = env!("PORT").to_string(); //ignore error in vs code, env is set
    |                            ^^^^^^^^^^^^
    |
    = help: use `std::env::var("PORT")` to read the variable at run time
    = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: environment variable `AES_KEY` not defined at compile time
   --> src\proto.rs:599:39
    |
599 |                 let encoded_aes_key = env!("AES_KEY");
    |                                       ^^^^^^^^^^^^^^^
    |
    = help: use `std::env::var("AES_KEY")` to read the variable at run time
    = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: environment variable `AES_KEY` not defined at compile time
   --> src\proto.rs:738:51
    |
738 | ...                   let encoded_aes_key = env!("AES_KEY");
    |                                             ^^^^^^^^^^^^^^^
    |
    = help: use `std::env::var("AES_KEY")` to read the variable at run time
    = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: environment variable `AES_KEY` not defined at compile time
   --> src\proto.rs:880:63
    |
880 | ...                   let encoded_aes_key = env!("AES_KEY");
    |                                             ^^^^^^^^^^^^^^^
    |
    = help: use `std::env::var("AES_KEY")` to read the variable at run time
    = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: could not compile `windows_ldr` (lib) due to 8 previous errors

[BabelQwerty]

sry for comment multi issue , bad network.

[Teach2Breach]

the errors are due to missing environment variables which are used at compile time, such as the SLEEP and ports, etc... When building implants from the conduit interface (logged in to the server), these values are added by the server at build time for each implant. If you want to build the implants on your own, without using the server build system, then you'll need to set the environment variables locally on the system where you are compiling. Set the values accordingly for your environment, with the IP and PORT being your server IP and 443, etc... The AES_KEY is printed to console by the anvil server on start, and is the value you should use when compiling an implant yourself. I'll be putting out some implants that are easy to build yourself (without the server) soon and some more documentation on this. Sorry for the confusion, things became more complex when I added AES. but for now it is suggested to build using the server and not compile implants locally, but if you just set the env vars, you still can.

[BabelQwerty]

thanks