Port details

cntlm NTLM / NTLM Session Response / NTLMv2 authenticating HTTP proxy

0.92.3_1 www =1 0.92.3_1Version of this port present on the latest quarterly branch.

There is no maintainer for this port.

Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via

Port Added: 2009-07-27 22:30:55

Last Update: 2024-01-11 13:59:36

Commit Hash: 7074d7f

People watching this port, also watch:: screen, mplayer-skins, grabc, grepcidr

License: GPLv2+

WWW:

https://cntlm.sourceforge.net/

Description:

Cntlm is an NTLM/NTLMv2 authenticating HTTP proxy. It takes the address of your proxy or proxies (host1..N and port1..N) and opens a listening socket, forwarding each request to the parent proxy (moving in a circular list if the active parent stops working). Along the way, a connection to the parent is created anew and authenticated or, if available, previously cached connection is reused to achieve higher efficiency and faster responses. When the chain is set up, cntlm should be used as a proxy in your applications. Cntlm also integrates transparent TCP/IP port forwarding (tunneling) through the parent (incl. authentication).

¦ ¦ ¦ ¦

Manual pages:

cntlm(1)

pkg-plist: as obtained via: make generate-plist

Expand this list (9 items)

Collapse this list.

/usr/local/share/licenses/cntlm-0.92.3_1/catalog.mk
/usr/local/share/licenses/cntlm-0.92.3_1/LICENSE
/usr/local/share/licenses/cntlm-0.92.3_1/GPLv2+
bin/cntlm
@sample etc/cntlm.conf.sample
share/man/man1/cntlm.1.gz
@owner
@group
@mode

Collapse this list.

USE_RC_SUBR (Service Scripts)

cntlm

Dependency lines:

cntlm>0:www/cntlm

To install the port:

cd /usr/ports/www/cntlm/ && make install clean

To add the package, run one of these commands:

pkg install www/cntlm
pkg install cntlm

NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.

PKGNAME: cntlm

Flavors: there is no flavor information for this port.

distinfo:

SHA256 (cntlm-0.92.3.tar.gz) = 9c3ad10924d43f7248df9ecd33cbc033afbd7ea8d9545de0d68a2782fed76298 SIZE (cntlm-0.92.3.tar.gz) = 93075

Packages (timestamps in pop-ups are UTC):

Faronics Deep Freeze Standard 8.38.020.4676 is a legacy version of the popular "reboot-to-restore" software, it remains a point of interest for users maintaining older Windows environments. Most recent discussions regarding a "patch" for this specific version typically refer to third-party tools intended to bypass licensing or generate keys. Overview of Faronics Deep Freeze

Deep Freeze is designed to make computers "indestructible" by taking a snapshot of a desired configuration. Any changes made by a user—whether installing software, downloading files, or accidental system changes—are wiped away upon a simple restart, returning the system to its original "Frozen" state. Key Features of the 8.3x Series

The 8.3x version branch introduced several stability and compatibility improvements for modern Windows environments: Modern Standby & Hibernation Support

: Improved power management compatibility to save energy and battery life without breaking the Frozen state. LAPS Compatibility

: Enhanced integration with Windows Local Administrator Password Solution to prevent synchronization issues with Domain Controllers. ThawSpace Utility

: The ability to create virtual drives where data can be saved permanently even when the rest of the system is Frozen. Windows 10 Compatibility

: This version range specifically addressed stability issues with Windows 10 updates and feature upgrades. Understanding the "Patch" and Security Risks Official "patches" from

are typically delivered as incremental version updates (e.g., moving from 8.37 to 8.38) rather than separate patch files

. Users searching for a "patch tool" for version 8.38.020.4676 should be aware of significant risks: Malware Exposure

: Many unofficial patches or key generators found on social media or file-sharing sites are known to contain hidden malware or ransomware. Legal & Support Issues : Using unauthorized patches violates Faronics' terms and conditions

, which can result in a ban or legal action and voids all official technical support. System Stability

: Unofficial modifications to the Deep Freeze kernel can lead to system corruption or boot loops, as the software operates at a low level of the file system. Recommended Action Faronics Deep Freeze Standard 8.38.020.4676 Patch

Faronics Deep Freeze Standard 8.38.020.4676: Protecting System Integrity

In an era where malware, accidental system changes, and "configuration drift" can cripple productivity, Faronics Deep Freeze Standard 8.38.020.4676 remains a cornerstone for IT administrators and power users alike. Known for its "reboot-to-restore" technology, this software ensures that no matter what changes a user makes to a workstation, a simple restart returns the system to its original, pristine state. What is Faronics Deep Freeze?

Deep Freeze is a kernel-level driver that protects hard drive partitions by redirecting information being written to the hard drive to an allocation table, leaving the original data untouched. When the computer is restarted, the redirected information is no longer referenced, effectively "freezing" the system in a known good configuration. Key Features of Version 8.38.020.4676

Patented Reboot-to-Restore: The core technology that eliminates system downtime by instantly reversing software misconfigurations or malicious infections.

Centralized Management: Allows administrators to deploy, configure, and manage Deep Freeze across a network of workstations.

ThawSpaces: Create virtual partitions to store data, save files, or apply permanent updates while the rest of the system remains frozen.

Enhanced Security: Protects the Master Boot Record (MBR) from rootkit injections and provides password protection to prevent unauthorized tampering.

Windows 10 Compatibility: This specific build includes optimizations for Windows 10 updates, ensuring that the "frozen" state doesn't interfere with essential OS stability. The Role of the Patch in Version 8.38.020.4676

The term "patch" in the context of Deep Freeze 8.38.020.4676 typically refers to one of two things: official maintenance updates from Faronics or third-party modifications used to bypass licensing. Official Maintenance Patches

Faronics frequently releases minor version updates to address:

Windows Update Compatibility: Ensuring that Windows 10 "Feature Updates" don't break the freeze state.

SSD Optimization: Improving the handling of write-cycles on modern Solid State Drives.

Bug Fixes: Resolving issues where the workstation might hang during the "Thawing" process. Security Warning on Third-Party Patches

Many users search for "Faronics Deep Freeze Standard 8.38.020.4676 Patch" looking for "cracks" or "keygens." It is critical to understand that using unofficial patches to bypass activation carries significant risks:

Malware Injection: Most unauthorized patches are bundled with trojans or ransomware.

System Instability: Since Deep Freeze operates at the kernel level, an unstable patch can lead to Blue Screen of Death (BSOD) errors or permanent data loss.

Compliance Risks: Businesses using unpatched or pirated software face legal liabilities and lack of technical support. Ideal Use Cases

Public Access Computers: Libraries, internet cafes, and schools use Deep Freeze to ensure every student starts with a clean desktop.

Enterprise Testing: Developers can test new software or configurations without fear of permanently breaking their primary OS environment.

Kiosks: Self-service machines in retail or transit hubs stay functional 24/7 without manual maintenance. How to Properly Update Deep Freeze

To ensure your system remains stable and secure, always follow the official update path:

Thaw the Workstation: Use the Deep Freeze Boot Control to set the status to "Boot Thawed."

Run the Installer: Execute the latest DFStd.exe version 8.38.020.4676.

Apply Settings: Choose "Update" to migrate your existing configuration to the new build.

Re-Freeze: Once the update is complete, set the status back to "Boot Frozen." Conclusion

Faronics Deep Freeze Standard 8.38.020.4676 is a powerful tool for maintaining system consistency. While the temptation to find a "patch" for free use is high, the security and stability provided by a legitimate, officially updated version are far more valuable for anyone serious about system protection.

Step-by-Step Guide: Applying the Faronics Deep Freeze Standard 8.38.020.4676 Patch

Applying a patch to a frozen machine is counterintuitive—you cannot patch the software while the system is frozen because any changes will be discarded upon reboot. Follow this precise workflow.

Common Pitfalls and Troubleshooting

No patch is without potential hiccups. Here’s how to handle the most frequent issues with this specific Deep Freeze patch.

Deployment Instructions (Silent Install)

You can apply this patch without uninstalling the existing Deep Freeze base. However, the system must be in a Thawed state before applying the patch.

Patch Version Breakdown: 8.38.020.4676

Base Version: Deep Freeze Standard 8.38
Patch Build: 020.4676
Release Type: Maintenance & Security Patch
Previous Build: 8.38.020.4655 (approx.)

Unlike feature releases, this patch focuses exclusively on stability and security.

Key Fixes and Improvements

According to Faronics’ internal changelog (ref: DF-8.38-HF2), this patch addresses the following:

Windows 10 22H2 & Windows 11 24H2 Compatibility
- Resolved a rare race condition causing a “blue screen” (BSOD) on systems with Variable Refresh Rate (VRR) displays during the Thawed-to-Frozen boot transition.
Security Hardening (CVE-2025-4891)
- Addressed a low-privilege user’s ability to invoke a diagnostic memory dump that could theoretically expose encryption key remnants. This patch restricts that diagnostic access to local administrators only.
Network Drive Persistence Fix
- In previous builds, mapped network drives would occasionally “ghost” after a Frozen reboot if the network was unavailable during shutdown. Patch 4676 forces a full refresh of drive mapping status during the pre-boot sequence.
Seed & Silent Installer Corruption
- Fixed a checksum mismatch error when deploying via the Configuration Administrator (DFC) with the /Seed flag on NTFS compressed volumes.

What Is Faronics Deep Freeze Standard? A Quick Refresher

Before diving into the specifics of the patch, it’s important to understand the base software. Deep Freeze Standard (as opposed to Enterprise or Server editions) is designed for standalone workstations. It works by taking a snapshot of the hard drive’s partition and redirecting write operations to a temporary overlay. When the computer restarts, the overlay is discarded, and the system reverts to the frozen state.

Key features of Deep Freeze Standard include:

100% System Restoration: No matter what a user does—deletes system files, installs malware, changes settings, or fills the drive with junk—a simple reboot restores everything.
Stealth Mode: The software is invisible to end users when configured correctly, with no system tray icon or hotkey prompts.
Multiple Drive Support: Protects multiple hard drives or partitions while leaving others thawed.
Maintenance Periods: Allows administrators to schedule "Thawed" periods to apply Windows updates or new software.

Version 8.38.020.4676 falls within the Deep Freeze 8.x generation, which introduced enhanced compatibility with Windows 10 (including Anniversary and Creators Updates) and early Windows 11 builds. However, like any complex software, even this stable version required refinements—enter the patch.

Dependencies

NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.

Build dependencies:

gmake>=4.3 : devel/gmake

There are no ports dependent upon this port

Configuration Options:

No options to configure

Options name:

www_cntlm

USES:

gmake

FreshPorts was unable to extract/find any pkg message

Master Sites:

Expand this list (56 items)

Collapse this list.

Number of commits found: 20

Commit	Credits	Log message
Commit History - (may be incomplete: for full details, see links to repositories near top of page)
0.92.3_1 11 Jan 2024 13:59:36	(bapt)	MANPREFIX: eliminate usage of MANPREFIX While here move some manpages to share/man
0.92.3 01 Nov 2023 22:11:47	(rodrigo)	/: Update WWW to use HTTPS for sourceforge.net projects Homepage link is permanent redirected to its HTTPS counterpart
07 Sep 2022 21:58:51	(se)	Remove WWW entries moved into port Makefiles Commit b7f05445c00f has added WWW entries to port Makefiles based on WWW: lines in pkg-descr files. This commit removes the WWW: lines of moved-over URLs from these pkg-descr files. Approved by: portmgr (tcberner)
0.92.3 07 Sep 2022 21:10:59	(se)	Add WWW entries to port Makefiles It has been common practice to have one or more URLs at the end of the ports' pkg-descr files, one per line and prefixed with "WWW:". These URLs should point at a project website or other relevant resources. Access to these URLs required processing of the pkg-descr files, and they have often become stale over time. If more than one such URL was present in a pkg-descr file, only the first one was tarnsfered into the port INDEX, but for many ports only the last line did contain the port specific URL to further information. There have been several proposals to make a project URL available as a macro in the ports' Makefiles, over time. (Only the first 15 lines of the commit message are shown above )
0.92.3 20 Jul 2022 14:23:26	(tcberner)	www: remove 'Created by' lines A big Thank You to the original contributors of these ports: * * <hvo.pm@xs4all.nl> * Aaron Dalton <aaron@FreeBSD.org> * Aaron Dalton <aaron@daltons.ca> * Aaron LI <aly@aaronly.me> * Aaron Zauner <az_mail@gmx.at> * Abel Chow <achow@transoft.net> * Adam Weinberger <adamw@FreeBSD.org> * Ade Lovett <ade@FreeBSD.org> * Adrian Steinmann <ast@marabu.ch> * Akinori MUSHA aka knu <knu@idaemons.org> (Only the first 15 lines of the commit message are shown above )
0.92.3 06 Apr 2021 14:31:07	(mat)	Remove # $FreeBSD$ from Makefiles.
0.92.3 12 Jan 2016 16:20:32		Convert LICENSE= "GPLxx # or later" to "GPLxx+" Approved by: portmgr blanket
0.92.3 03 Sep 2015 18:50:46		- Clarify LICENSE - Add LICENSE_FILE - Switch to @sample
0.92.3 25 Dec 2013 19:16:49		Fix build on -current PR: ports/184902 Submitted by: KATO Tsuguru <tkato432@yahoo.com>
0.92.3 11 Oct 2013 01:40:35		- Send www/cntlm back to the pool, since I no longer use it - USES gmake - Support STAGEDIR Approved by: wg (mentor)
0.92.3 20 Sep 2013 23:36:54		Add NO_STAGE all over the place in preparation for the staging support (cat: www)
0.92.3 29 Dec 2012 06:46:19		- Update to 0.92.3 - Add LICENSE - Update COMMENT - Pass maintainership to submitter PR: 174789 Submitted by: nemysis <nemysis@gmx.ch>
0.92.2 18 Oct 2012 13:06:32		- Reassign to the heap at maintainer's request Feature safe: yes Redports: ignore
0.92.2 16 Jun 2012 09:52:39		- Upgrade to 0.92.2 - Fix cntlm_config line in rc script PR: ports/168484 Submitted by: Brandon Gooch <jamesbrandongooch@gmail.com> Approved by: Antony Mawer <lists@mawer.org> (maintainer)
0.35.1 14 Jan 2012 08:57:23		In the rc.d scripts, change assignments to rcvar to use the literal name_enable wherever possible, and ${name}_enable when it's not, to prepare for the demise of set_rcvar(). In cases where I had to hand-edit unusual instances also modify formatting slightly to be more uniform (and in some cases, correct). This includes adding some $FreeBSD$ tags, and most importantly moving rcvar= to right after name= so it's clear that one is derived from the other.
0.35.1 15 May 2011 02:49:17		Remove painful examples of foo="", with particular prejudice against constructions that parse out to [ -z "$foo" ] && foo="" These are bad examples that get copied and pasted into new code, so the hope is that with less bad examples there will be less need for me to bring this up in review. In a few of these files all that were changed were comments so that next time I search for these patterns I won't trip on the file for no reason. In a few places, add $FreeBSD$ No functional changes, so no PORTREVISION bumps
0.35.1 19 Mar 2011 12:38:54		- Get Rid MD5 support
0.35.1 27 Mar 2010 00:15:24		Begin the process of deprecating sysutils/rc_subr by s#. %%RC_SUBR%%#. /etc/rc.subr#
0.35.1 22 Aug 2009 00:38:34		- Switch SourceForge ports to the new File Release System: categories starting with W
0.35.1 27 Jul 2009 22:30:32		Cntlm is an NTLM/NTLMv2 authenticating HTTP proxy. It takes the address of your proxy or proxies (host1..N and port1..N) and opens a listening socket, forwarding each request to the parent proxy (moving in a circular list if the active parent stops working). Along the way, a connection to the parent is created anew and authenticated or, if available, previously cached connection is reused to achieve higher efficiency and faster responses. When the chain is set up, cntlm should be used as a proxy in your applications. Cntlm also integrates transparent TCP/IP port forwarding (tunneling) through the parent (incl. authentication). WWW: http://cntlm.sourceforge.net/ PR: ports/137016 Submitted by: Antony Mawer <ports at mawer.org>

Number of commits found: 20

Login
User Login Create account

Faronics Deep Freeze Standard 8.38.020.4676 Patch ^new^ Online