node-authenticate-pam
node-authenticate-pam copied to clipboard
Rush
Asynchronous PAM authentication for NodeJS
see https://huntr.dev/bounties/09fb00bd-d95e-4cc5-a989-0ee0960922da/ fix is based on https://github.com/github/codeql/blob/bbd7e623418e41775c90cfbbe44ad25b3bf9c5e3/cpp/ql/src/experimental/Security/CWE/CWE-285/PamAuthorizationGood.cpp
Hi, because webpack by default only loads js and json files i get this error: > ERROR in ./node_modules/authenticate-pam/build/Release/authenticate_pam.node 1:0 Module parse failed: Unexpected character '' (1:0) You may need...
Hi, i can't install authenticate-pam. It failes with the following log. node and nodejs are v12.22.1. ```` npm install authenticate-pam > [email protected] install /opt/iobroker/node_modules/authenticate-pam > node-gyp rebuild make: Entering directory...
``` make: Wejście do katalogu '/home/panel/node_modules/authenticate-pam/build' CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o In file included from ../authenticate_pam.cc:23:0: ../../nan/nan.h:324:47: error: ‘REPLACE_INVALID_UTF8’ is not a member of ‘v8::String’ static const unsigned kReplaceInvalidUtf8 = v8::String::REPLACE_INVALID_UTF8; ^ authenticate_pam.target.mk:84:...
is there any way in this package to know about the user access level on a host machine??
The replacement is safe and it is strongly advised according the new https://github.com/nodejs/nan APIs https://github.com/nodejs/nan/blob/master/doc/node_misc.md#api_nan_asyncresource @WeiAnAN was definitely right in making this crucial modification
``` > [email protected] postinstall /opt/os.js/node_modules/node-sass > node scripts/build.js Binary found at /opt/os.js/node_modules/node-sass/vendor/linux-x64-67/binding.node Testing binary Binary is fine npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL...
Hi I know issue about crash when run as non root users is known. But do you have any clue where it happen in libpam? I'm facing the same issue...
I get the above error everytime I login with an existing user, not with an invalid user. Any Idea what is happening there and what part tries to access this...
One thing I noticed is an exception is thrown from PAM when there an attempt to login with a user that does not exist. https://github.com/Rush/node-authenticate-pam/blob/master/authenticate_pam.cc#L114 Should maybe that error be...
