Bug 290932 - security/pecl-mcrypt: update to 1.0.9
Summary: security/pecl-mcrypt: update to 1.0.9
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Luca Pizzamiglio
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-10 18:54 UTC by R. Christian McDonald
Modified: 2025-11-11 16:28 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (pizzamig)

Attachments
update to 1.0.9 (1.46 KB, text/plain)
2025-11-10 18:54 UTC, R. Christian McDonald 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description R. Christian McDonald freebsd_committer freebsd_triage 2025-11-10 18:54:22 UTC 
Created attachment 265314 [details]
update to 1.0.9
Comment 1 R. Christian McDonald freebsd_committer freebsd_triage 2025-11-10 18:55:01 UTC 
1.0.9 includes native support for PHP 8.4, so we also drop the local patch.
Comment 2 R. Christian McDonald freebsd_committer freebsd_triage 2025-11-10 18:55:16 UTC 
1.0.9 includes native support for PHP 8.4, so we also drop the local patch.
Comment 3 Paavo-Einari Kaipila 2025-11-11 02:12:30 UTC 
Would it be time to deprecate this? Mcrypt has been dead for 20 years.

PHP extension does have several consumers at least on paper. I'm 100% sure matomo doesn't actually need this and I'd be surprised if others did.

pear-Crypt_CHAP is an exception and actually needs mcrypt. Like almost all pear-* ports however, it is an unmaintained one and code in it doesn't even run anymore (yes I tried).
Comment 4 R. Christian McDonald freebsd_committer freebsd_triage 2025-11-11 16:28:31 UTC 
(In reply to Paavo-Einari Kaipila from comment #3)
Yes it should be deprecated at this point, but there are still consumers of this that need more time to transition.