Erlend Tobiassen

I tested the null check on the first indirection and I unfortunately the assertion failed immediately. > thread 'main' panicked at 'assertion failed: unsafe { !(*env_ptr).is_null() }', /home/alan/dev/regiontog/pam/src/env.rs:52:13 I know...

> That's interesting which test did you run? I just ran my DM, I did not check if too closely but I assume it was the `initialize_environment` called from `open_session`...

Another more intuitive way would be to set the PAM_USER in the set_credentials function. And that is what I wanted to do originally. The problem with that is that the...

> That can be fixed by passing the handle as `appdata_ptr` although I am not sure if we can call arbitrary PAM functions inside of the conversation function. The man...

> We would have to copy the handle to the `PasswordConv` struct which would certainly be possible `set_item` needs a mutable reference to the `PamHandle` so I had to make...

> Some minor comments and afterwards this should be ready. > I am not quite sure about the API, so I might iterate some more on it (`pam` is 0.X...

Depending on how general this library wants to be passing in those as arguments to `open_session` could work. I don't really know pam that well so afaik `open_session` could be...

I had the same issue and did some digging. Seems like this error occurs when the `repoRootForImportPath` function in go-get fails to identify the kind of vcs system behind the...