>> This looks like a jump to null in the RC4 logic using EVP_md4().
>>
>> For EVP_rc4 we have a hack in Heimdal to do
>>
>> EVP_CIPHER_fetch(NULL, "rc4", "provider=legacy")
I don't know if you have control over this, but ... RC4? In 2023? Yikes.
Kerberos clients do send a list of the supp
>so in actual usage pretty well everything is going to use
>aes256-cts-hmac-sha1-96 (unless you have a really old client out there)
>but the KDC is still going to create or update keys of all three types,
>and that is whats failing here.
My apologies; going back I realize I conflated the client
> Hello Taylor. Just as a point of reference, smtp clients that
>connect to domains hosted by Microsoft, i.e. outlook.com and any other
>domains that use their infrastructure for e-mail, will have to present
>a valid SSL certificate in order to submit mail to their smtp servers.
I do not be
> hello Ken. It may be that the RFC says the client need not
>present a valid certificate, but I have found that smtp clients I
>manage that want to send mail to Microsoft managed domains cannot set
>up an SSL encrypted smtp session unless the client presents a valid
>certificate as part of
> hello Ken. Yes, I missed that part of what you were trying to
>say. You're right, I didn't try that. I'm not sure that's possible
>when configuring SSL with sendmail.
It looks like as long as you have the "O ClientCertFile" and
"O ClientKeyFile" options commented out it won't use one in
>Governor Matt Bevin of Kentucky didn't want to remove the offending
>statues because that would only serve to sanitize history. I agree
>with that viewpoint.
I'd be sympthatic to that argument if a) we weren't talking about
monuments to people who were leading an armed insurrection against the
g
>>Hello. A /bin/sh script I wrote about 10 years ago under NetBSD-5
>>broke under NetbSD-10.99.12. The issue seems to be a change in the way
>>command line arguments are assigned to the $number variables, i.e. $1,
>>$2, $3, etc.
>
>Looks to me like $11 is being interpreted as ${1}1. I wonder wha
>Hello. A /bin/sh script I wrote about 10 years ago under NetBSD-5
>broke under NetbSD-10.99.12. The issue seems to be a change in the way
>command line arguments are assigned to the $number variables, i.e. $1,
>$2, $3, etc.
Looks to me like $11 is being interpreted as ${1}1. I wonder what ${11
