Pingvin Share inventory should include proxy trust settings
Pingvin Share is a self-hosted file-sharing service with public share links, reverse shares, and optional OIDC or LDAP authentication. That combination makes it a convenient front door for receiving and distributing files. It also means the deployment has to decide which requests are public, which require an account, and which proxy headers the application may trust.
On 2026-11-09, ZoomEye returned 1,189 matches for title="Pingvin Share". The body query returned 2,820 and the app query returned zero. The title query is the selected inventory signal. The body count may include references that are not running instances, so it is not used as the primary count.
These observations describe matching assets in the selected scope. They do not establish that a page is an active installation or that anonymous uploads are enabled.
Reverse proxy settings are security settings
Pingvin Share's configuration includes TRUST_PROXY, which controls whether the application is behind a reverse proxy. The setting affects how the application interprets forwarded requests. Operators should enable it only when the proxy is known, the client cannot reach the backend directly, and the proxy strips and replaces forwarded headers according to a defined policy.
An identity-aware proxy can be a strong access layer. It can also create false confidence if the backend remains directly reachable. Test the service from the public network, from the proxy network, and from a direct backend address. Confirm that a request carrying forged forwarding headers cannot change the application's idea of the client or the authenticated user.
Decide what public sharing means
Public links are a product feature. Reverse shares and anonymous upload are separate decisions. Review whether an unauthenticated person can create a share, choose an arbitrary retention period, or consume unlimited storage. Set limits on file size, total storage, concurrent uploads, and expiry. Use a separate storage volume and quota for public uploads if the platform permits.
If OIDC or LDAP is enabled, map provider claims to local roles. A user who can log in should not automatically be an administrator. Review who can change global settings, manage users, and see all shares. If email is configured, protect SMTP credentials and verify the recipient link domain.
Monitor data flow
Log share creation, uploads, downloads, authentication events, configuration changes, and proxy errors. Track outbound volume and the ratio of uploads to downloads. A file-sharing service can look healthy while it is being used to move data outside the expected boundary.
Inventory the application with the host owner, version, authentication mode, proxy setting, public link policy, and storage backend. Check whether the default or example configuration has been copied into production with a broad public path.
Test an anonymous visitor, a normal user, an administrator, and a direct backend request. Verify that the public share path works without exposing administrative endpoints. The count is modest, but the consequence of a weak share policy can be large because the service is designed to move files across a trust boundary.
