forked from unom/punktfunk
enricobuehlerandClaude Opus 5
553676282a
Device Manager, the firewall list and the monitor name all said "punktfunk". The brand
is Punktfunk.
Renamed: the [Strings] blocks of all four driver INFs (device descriptions, install
disks, provider, manufacturer), the `description` on every SwDeviceProfile the host
creates, pf-mouse's HID manufacturer + product strings, pf-vdisplay's IddCx endpoint
friendly + manufacturer names, the EDID 0xFC display-name descriptor — so Windows now
shows `Generic Monitor (Punktfunk)` — and the netsh firewall rule names.
The EDID edit is a single byte (0x70 -> 0x50) and needs no hand-patched checksum:
Edid::generate_with already recomputes both block checksums after patching the serial.
Deliberately left lowercase, because these are IDENTITIES rather than display names and
renaming them would orphan installed state:
* the SwDeviceCreate enumerator `w!("punktfunk")` — it IS the SWD\PUNKTFUNK\... path
every pad instance id is built from
* pf-paths' `join("punktfunk")` — C:\ProgramData\punktfunk
* the CN=punktfunk-driver cert subject, which purge_driver_certs and both driver build
scripts match by string
* install.rs' `lo.contains("punktfunk virtual display")` probes, whose haystack is
to_ascii_lowercase()d, so they already match the capitalised name
Nothing is orphaned by the renames that DID happen either: netsh rule names,
Get-NetFirewallRule -DisplayName and PowerShell's -match are all case-insensitive, so
the firewall delete paths and reset-pf-vdisplay.ps1's -AdapterName / -GhostMatch
defaults still reap what every release up to 0.22.1 created.
Cosmetic, with two consequences worth knowing: it takes a driver rebuild + re-sign to
appear at all, and an existing devnode keeps its cached FriendlyName until it is
recreated.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
87 lines
2.7 KiB
Plaintext
87 lines
2.7 KiB
Plaintext
;/*++
|
|
; pf-vdisplay - punktfunk virtual display, UMDF2 IddCx driver INF (template; stampinf -> .inf).
|
|
;
|
|
; For the all-Rust wdk-sys / windows-drivers-rs driver in THIS tree
|
|
; (packaging/windows/drivers/pf-vdisplay/). The driver registers the OWNED pf_driver_proto
|
|
; control-interface GUID in CODE (WdfDeviceCreateDeviceInterface), so this INF is GUID-agnostic and
|
|
; is byte-identical to the superseded oracle's (packaging/windows/vdisplay-driver/.../pf_vdisplay.inx,
|
|
; itself adapted from MolotovCherry/virtual-display-rs (MIT) + SudoVDA's control-device security DACL).
|
|
; HWID Root\pf_vdisplay + IddCx0102 + the DACL match the host backend (crates/punktfunk-host/src/
|
|
; vdisplay/pf_vdisplay.rs) and install-pf-vdisplay.ps1's Test-PfVdisplayPresent / nefconc node-create.
|
|
;--*/
|
|
[Version]
|
|
PnpLockdown=1
|
|
Signature="$Windows NT$"
|
|
ClassGUID={4D36E968-E325-11CE-BFC1-08002BE10318}
|
|
Class=Display
|
|
ClassVer=2.0
|
|
Provider=%ManufacturerName%
|
|
CatalogFile=pf_vdisplay.cat
|
|
DriverVer=
|
|
|
|
[Manufacturer]
|
|
%ManufacturerName%=Standard,NT$ARCH$
|
|
|
|
[Standard.NT$ARCH$]
|
|
%DeviceName%=pf_vdisplay_Install, Root\pf_vdisplay
|
|
|
|
[SourceDisksFiles]
|
|
pf_vdisplay.dll=1
|
|
|
|
[SourceDisksNames]
|
|
1=%DiskName%
|
|
|
|
; =================== UMDF IddCx device ====================
|
|
|
|
[pf_vdisplay_Install.NT]
|
|
CopyFiles=UMDriverCopy
|
|
|
|
[pf_vdisplay_Install.NT.hw]
|
|
AddReg=pf_vdisplay_HardwareDeviceSettings
|
|
|
|
[pf_vdisplay_HardwareDeviceSettings]
|
|
HKR, , "UpperFilters", %REG_MULTI_SZ%, "IndirectKmd"
|
|
HKR, "WUDF", "DeviceGroupId", %REG_SZ%, "pfVDisplayGroup"
|
|
; Only the host (LocalSystem service) + admins may open the control device. Deliberately NO Everyone
|
|
; ACE (SudoVDA ships one for its user-mode host): the control plane creates/removes monitors and
|
|
; bootstraps the sealed frame channel (IOCTL_SET_FRAME_CHANNEL), so it is not for unprivileged callers.
|
|
HKR, , "Security", , "D:P(A;;GA;;;SY)(A;;GA;;;BA)"
|
|
|
|
[pf_vdisplay_Install.NT.Services]
|
|
AddService=WUDFRd,0x000001fa,WUDFRD_ServiceInstall
|
|
|
|
[pf_vdisplay_Install.NT.Wdf]
|
|
UmdfService=pf_vdisplay, pf_vdisplay_Install
|
|
UmdfServiceOrder=pf_vdisplay
|
|
UmdfKernelModeClientPolicy=AllowKernelModeClients
|
|
UmdfHostProcessSharing=ProcessSharingDisabled
|
|
|
|
[pf_vdisplay_Install]
|
|
UmdfLibraryVersion=$UMDFVERSION$
|
|
ServiceBinary=%12%\UMDF\pf_vdisplay.dll
|
|
UmdfExtensions=IddCx0102
|
|
|
|
[WUDFRD_ServiceInstall]
|
|
DisplayName=%WudfRdDisplayName%
|
|
ServiceType=1
|
|
StartType=3
|
|
ErrorControl=1
|
|
ServiceBinary=%12%\WUDFRd.sys
|
|
|
|
[DestinationDirs]
|
|
UMDriverCopy=12,UMDF
|
|
|
|
[UMDriverCopy]
|
|
pf_vdisplay.dll
|
|
|
|
[Strings]
|
|
ManufacturerName="Punktfunk"
|
|
DiskName="Punktfunk Virtual Display Installation Disk"
|
|
WudfRdDisplayName="Windows Driver Foundation - User-mode Driver Framework Reflector"
|
|
DeviceName="Punktfunk Virtual Display"
|
|
|
|
REG_MULTI_SZ=0x00010000
|
|
REG_SZ=0x00000000
|
|
REG_EXPAND_SZ=0x00020000
|
|
REG_DWORD=0x00010001
|