We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On Linux, using Ruby 3.2.2, getting shadow.so: undefined symbol: rb_tainted_str_new2 with ruby-shadow-ruby32-2.5.1.gem.
The following code in this gem uses rb_tainted_str_new2: pwd/shadow.c:59: rb_tainted_str_new2(entry->pw_name), /* sp_namp / pwd/shadow.c:60: rb_tainted_str_new2(entry->pw_passwd), / sp_pwdp, encryped password / pwd/shadow.c:69: rb_tainted_str_new2(entry->pw_class), / sp_loginclass, user access class */ shadow/shadow.c:37: rb_tainted_str_new2(entry->sp_namp), shadow/shadow.c:38: rb_tainted_str_new2(entry->sp_pwdp),
It needs to be fixed similar to ruby-odbc's: vhermecz/ruby-odbc@c38d182
Can we get the ruby-shadow-ruby32 patched to resolve this issue?
Thanks.
The text was updated successfully, but these errors were encountered:
FYI - this error occurs when using https://github.com/ticketsolve/ruby-shadow-ruby32
Sorry, something went wrong.
This should be resolved with #29 .
No branches or pull requests
On Linux, using Ruby 3.2.2, getting shadow.so: undefined symbol: rb_tainted_str_new2 with ruby-shadow-ruby32-2.5.1.gem.
The following code in this gem uses rb_tainted_str_new2:
pwd/shadow.c:59: rb_tainted_str_new2(entry->pw_name), /* sp_namp /
pwd/shadow.c:60: rb_tainted_str_new2(entry->pw_passwd), / sp_pwdp, encryped password /
pwd/shadow.c:69: rb_tainted_str_new2(entry->pw_class), / sp_loginclass, user access class */
shadow/shadow.c:37: rb_tainted_str_new2(entry->sp_namp),
shadow/shadow.c:38: rb_tainted_str_new2(entry->sp_pwdp),
It needs to be fixed similar to ruby-odbc's: vhermecz/ruby-odbc@c38d182
Can we get the ruby-shadow-ruby32 patched to resolve this issue?
Thanks.
The text was updated successfully, but these errors were encountered: