scd-event is annoying to use on Windows
Closed, WontfixPublic


scd-event is usable on Windows, however as far as I can tell, the file must be
a native executable (something with a MZ header). I've made a simple program
which modifies argv[0] to append ".cmd" and otherwise forward the process
creation via system(). This allows editing scd-event.cmd on the fly which is a
lot nicer, but this solution really should not be necessary. If gnupg properly
created a new process, then a user could put any executable/script at the scd-
event location and have it work (which is the expected behavior). On windows,
this may require being able to change the filename which gnupg uses for scd-
event (in order to provide a system-recognizable extension). I tried making scd-
event a symlink but this did not work either.

shuffle2 added a subscriber: shuffle2.
werner added a subscriber: werner.Feb 14 2017, 3:21 PM

Never use system() anywhere!

You need to call cmd with the script. However, there are some security issues
with than too and thus I consider it better use a dedicated executabe for this.

If you can tell us what the script shall do, we may distribute a simple
executable for that purpose.

marcus closed this task as Wontfix.Jul 27 2017, 3:18 PM
marcus claimed this task.