Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
== Introduction
Phusion Passenger probably requires no introduction. We kindly refer the reader to http://www.modrails.com/ for general information.
== Installation
=== Regular installation
You can install either Phusion Passenger for Apache or for Nginx. Run either of the following programs as root:
./bin/passenger-install-apache2-module
-OR-
./bin/passenger-install-nginx-module
That's it. :)
For troubleshooting, configuration and tips, please read the corresponding Users Guide:
doc/Users guide Apache.html doc/Users guide Nginx.html
These files are included in the source tarball, and may also be viewed online on our website.
=== Installing via a gem
You may also first generate a .gem file, and then install that. First, make sure that you have the following software installed:
Next, run:
rake package
The gem will be available under the 'pkg' folder.
== Legal
Phusion Passenger is a trademark of Hongli Lai & Ninh Bui.
FAQs
Unknown package
We found that yspassenger demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.