On Sat, 25 Jan 2025 at 01:26, Shane Curcuru <a...@shanecurcuru.org> wrote: > > sebb wrote on 1/24/25 8:04 PM: > > On Sat, 25 Jan 2025 at 00:45, Shane Curcuru <a...@shanecurcuru.org> wrote: > >> > >> sebb wrote on 1/24/25 6:39 PM: > >>> On Fri, 24 Jan 2025 at 20:01, <curc...@apache.org> wrote: > ...snip... > > > Then use codesign -f -s, for example: > > sudo codesign -s "Cert Name" -f > > /opt/homebrew/opt/passenger/libexec/buildout/apache2/mod_passenger.so\ > > Yup, I followed similar advice (below), but that codesign gives me an > error that the module is already signed, so fails.
The -f flag overrides any existing certificate. Note also the you don't need to run a server or passenger to test most cgi scripts. They can be run on the command-line. Redirect output to an HTML file and then open that. You might need to pass in some environment variables, e.g. $ QUERY_STRING=xxxx ruby script.cgi > script.html $ open script.html > Researching how > homebrew signs modules showed a lot of bits about how they're changing > things, but not the details of how to validate or use their signatures. > > https://blog.phusion.nl/2020/12/22/future_of_macos_apache_modules/ Useful > I'm trying to get the energy up to fork, patch, and build a ruby-ldap3 > module and put it on rubygems, and then test simply using that (patched, > fixed for ruby 3.x) version, instead of monkey patching locally. > > -- > - Shane > Member > The Apache Software Foundation >
