Bradley Landherr

@jodimary Did you also build the driver and place it in the path defined at: https://github.com/landhb/HideProcess/blob/master/loader/loader.c#L8 You can change that define statement to point to wherever your .sys file is.

No problem! Hope it helps, good luck!

I'm not sure what you mean by that. There aren't any specific instructions used that wouldn't be emulated by a hypervisor. I just tested this on the latest Windows 10...

@Mecanik, because this project doesn’t bypass PatchGuard the blue screen will occur on any x64 windows build newer than Windows XP SP1. “In x64 editions of Windows, Microsoft began to...

@Mecanik Just noticed you said x32. My fault! Let me see if I can find that build and spin up a VM over the weekend. Do you have any other...

One note I noticed on the interface. Instead of having a mutable global that requires users to call: ```rust // set the proper backend keyring::set_default_credential_builder(Box::new(LinuxNativeCredentialBuilder)); // start an entry let...

For the mock usage, users could do something like: ```rust #[cfg(test)] let entry = Entry::new_with_builder(&MockBuilder, "myservice" , "keyid-2")?; #[cfg(not(test))] let entry = Entry::new("myservice" , "keyid-2")?; ```

@brotskydotcom `new_with_credential` definitely fits that need as well. My thought process was if the library user can use the `Entry` API with their own builder then there may not be...

Is the `secret-service` crate fully removing their blocking interface? https://github.com/hwchen/secret-service-rs/tree/master/src/blocking

@Sytten would this not work for async applications using `keyring-rs`? ```rust use keyring::{Entry, Error}; fn get_credential() -> Result { // This call blocks in zbus::blocking let entry = Entry::new("test", "test2")?;...