Your message dated Mon, 2 May 2022 08:32:02 +0200 with message-id <20220502063202.GA196183@devrim> and subject line Re: Bug#1010425: opendkim-tools: opendkim-genkey ignores commandline options. has caused the Debian Bug report #1010425, regarding opendkim-tools: opendkim-genkey ignores commandline options. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1010425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010425 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: opendkim-tools Version: 2.11.0~beta2-4 Severity: important Hello, opendkim-genkey seems to ignore all commandline options: 8X------------ ametzler@vsrv21575:~$ /usr/sbin/opendkim-genkey −−selector=be1 −b 1024 −D /tmp --verbose opendkim-genkey: generating private key opendkim-genkey: private key written to default.private opendkim-genkey: extracting public key opendkim-genkey: DNS TXT record written to default.txt ametzler@vsrv21575:~$ ls -l /tmp/be1.* /tmp/default.* `pwd`/default.* ls: cannot access '/tmp/be1.*': No such file or directory ls: cannot access '/tmp/default.*': No such file or directory -rw------- 1 ametzler ametzler 1679 1. Mai 11:39 /home/ametzler/default.private -rw------- 1 ametzler ametzler 505 1. Mai 11:39 /home/ametzler/default.txt ametzler@vsrv21575:~$ head -n1 /home/ametzler/default.txt default._domainkey IN TXT ( "v=DKIM1; h=sha256; k=rsa; " ametzler@vsrv21575:~$ certtool --infile=default.private --key-info | grep bits Key Security Level: Medium (2048 bits) 8X------------ cu Andreas
--- End Message ---
--- Begin Message ---You are using the Unicode minus sign instead of the hyphen. Notice the difference: −−selector --selector When you use the hyphen then these options are working fine. Apparently, your arguments are treated as unknown and are ignored. A better user experience might be some kind of warning. I think such a change could be suggested upstream. Cheers,
--- End Message ---
