No, the commands (if any) don't need to be protected at all, if they don't have 
the HMAC of the secret or password, then it's meaningless what they send to 
have executed because it will never be read or processed.

Why protect a script of commands, they aren't secret in any way.  

In this case, even if someone can think of a way to fool SPF, and DKIM, andn 
DMARC, they would also need to not only have to create a valid HMAC (which in 
my case expires after a predetermined time set by the site), but they also have 
to know what the secret or password was that is contained within the HMAC SSL 
protected string.  

The chances of getting past all of that is so close to zero that it's 
meaningless to even think about the possibility.

Brian 

On Sat, 29 Aug 2026 23:22:05 +0100, Jeremy Nicoll 
<[email protected]> wrote:

>On Thu, 27 Aug 2026, at 05:53, Brian Westerman wrote:
>> Yes, I got it.  I have created a web interface that doesn't really use
>> the web, it just needs a web browser to generate the auth key (they
>> type their key and it uses OPENSSL to generate and autocopies it to the
>> clipboard, then the person who wants to send the commands just pastes
>> it into their email.
>
>I thought the idea is that generation of the HMAC would need to take as
>input both the secret AND the string(s) of the command(s)?
>
>It wouldn't work if you generated the HMAC & then pasted that into the email
>alongside arbitrary (or if you like: yet to be defined) command text.
>
>--
>Jeremy Nicoll - my opinions are my own.
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to