Actually, Jack, it is in the clear in the .mac file, I suppose because I'm not saving a password, I'm saving a macro that has text in it that happens to be a password. This is at least what I've seen for some time now. I do seem to recall a setting in maybe the non-ACS version for encrypting something in the .mac file, but I don't see it in the HOD-based ACS emulator. That might mean requiring that I record the macro again for a change, not sure. And that'd be kind of awkward.
I did just try changing an innocuous, harmless bit in the macro - there's a "description" element, I just added a digit 1 to the end of the value when editing in, say, Session A. Then I closed down all 4 sessions and exited from it. Then when I restarted the ASC batch, lo and behold, the change was there.
So I am sure that there is exactly 1 copy of the macro - that is all that really makes sense. But the interface must have a cache of the contents of the macro, and that cache is what controls what populates the editor window on "opening", so it looks like the edit didn't take - or something.
In any case, the interface is not showing reality, and I take this to be a bug. If something is cached and then the thing that fed the cache is changed, the cache should be changed, seems to me.
Thanks for the good thoughts! See you in a few!
Vern
On Mon, 13 Nov, 2023 at 9:22 PM, Jack Woehr via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
To: midrange systems technical discussion
Cc: jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx; vhamberg@xxxxxxxxxxxxxxx
On Mon, Nov 13, 2023 at 1:14 PM VERNON HAMBERG Owner via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>> wrote:
Never store any sign-on information, especially passwords, in any PC files
such as "macros" as this could potentially lead to a breach of security, if
someone is able to read data on your PC, e.g. those macro definitions.
Passwords in IBM i Access Client Solutions macros are automatically
encrypted. iACS detects you're saving a password and encrypts it.
midrange.com
