Page MenuHome GnuPG

GpgEX: Unicode in file or foldername causes error
Open, NormalPublic


When a more than 8 bit unicode character is present in a file or folder name, encryption via GpgEX does not work, error is "Error returned by the GnuPG user interface: no such file or directory":



Event Timeline

ebo added projects: Restricted Project, gpgex.
ebo renamed this task from GpgEX: Unicode in file or foldername to GpgEX: Unicode in file or foldername causes error.Sep 20 2023, 4:34 PM
aheinecke triaged this task as Normal priority.
aheinecke added a subscriber: aheinecke.

Not sure yes If I rather fix this or do: T6331

This is not a regression AFAIR I think it has been this way since I started working on Gpg4win.

Edit: The text below was wrong. The error given below only occurs when the combined path+filenmae is to long on windows.
An emoticon in a file below the folder to be encrypted does not hinder encryption via GpgEX.

Btw: This occurs also with emoticons in the folder one level above the files to be encrypted.

In that case you do not get an immediate error message, only after you have chosen the recipients you get a general error for the signing part of sign/encrypt and the corresponding error in the log viewer in this case starts with gpgtar: error stat-ing