[Info-vax] What to do with my VAX.....

[seasoned_geek]

On Friday, November 20, 2020 at 7:10:37 PM UTC-6, Arne Vajhøj wrote:
> On 11/20/2020 7:59 PM, Arne Vajhøj wrote: 
> > On 11/20/2020 9:46 AM, seasoned_geek wrote: 
> > And with a decent implementation all bytes should change.
> And if anyone want to verify that it does. 
> 
> Just do: 
> 
> $ mcr ssl1$exe:openssl enc -aes-256-cbc -k MySuperSecretPassPhrase -P 
> -md sha1 
> 
> on your favorite OS a few times. 
> 
> I got: 
> 
> iv =0E38C5B4A04DAD98965D95161268ECDB 
> iv =51D9A670DEB1BF1E56745D28A6441A3C 
> iv =26E6C8F59628C12A7A4EBFC3BF340727 
> iv =E4609B2D4AFD0B8190101A87F8CA83DB 
> iv =9350E05D92C0915B229048B251E3C663 
> 
> They look quite different to me. 
> 

You know Arne, some people shouldn't be allowed to buy a keyboard and you are one. Once again you have veered off into the weeds ignoring details that didn't fit into your tiny mind.

NONE of this has __anything__ to do with what I originally stated about SSL/TLS having a TOD sensitivity on Ubuntu. In particular I noticed it on 18.04 but it might also exist in 20.04 LTS, I just haven't had time to look into it.

Guess what? When the "maintainer" decided to "help out the upstream" some years back by cleaning up that compilation warning, only YABUs had a 32-bit limit. You couldn't replicate that problem on VMS either.

I have asked you repeatedly to never comment on my messages because you know less than nothing and READ EVEN LESS.