Re: How to do FTP using TN5250 Mochasoft

Hi Glenn,

I'm curious if "caproate" was not a typo, what do you mean?

If you're using Windows or Linux (which generally use ASCII) and connecting to an IBM i (which uses EBCDIC) and you're in the U.S., it probably is not a problem, because an @ symbol in ASCII is x'40', and it would get translated to EBCDIC as x'7C', the value for @ in ccsid 37.

It sounded like Tim's problem was that pub400.com uses ccsid 273, which is also EBCDIC, but for Austria/Germany, and it has the value x'B5' for @.  When he keyed @ into his Mochasoft emulator, it apparently translated it to x'B5' (the value for ccsid 273), and he was able to signon with no problem.  When he used iACS emulator, it was configured to use ccsid 37, and translated @ from x'40' to x'7C' and that obviously did not match the password he entered with Mochasoft.

Tim mentioned changing the configuration for iACS to ccsid 273 and reported that it still failed. I'm not sure if that's because iACS ignored the configuration value, or needed to be restarted after the change, or what.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx
pdow@xxxxxxxxxxxxxx /

On 5/30/2023 2:47 PM, Glenn Ericson wrote:

I've used @ iin passwords as caproate without a problem
Glenn Ericson 718 898 9805gericson@xxxxxxxxxxxx
On Tuesday, May 30, 2023 at 05:14:44 PM EDT, Buck Calabro<kc2hiz@xxxxxxxxx> wrote:
On 5/30/2023 4:05 PM, John Yeung wrote:

I don't think the expectation to be *able* to use '@' in a password
necessarily has to do with wanting to recycle. I think it mainly has
to do with the idea that using "special characters" increases password
strength. And this idea is reinforced by many sources.

At the risk of excessive thread drift, I use a password manager, and I
tell it to generate a random 32 character password for a new account.
That random string definitely has special characters including '@'. Yes,
it's adjustable both is terms of length and composition, but more of
each is better at slowing down brute force and rainbow attacks.

Personally, I don't see the solution to this behaviour as simple as
'choose another character in your password.' How would I maintain a
database of email addresses?

I guess the big picture answer is that I need to know the CCSID of the
target system/job/user and set up a specific ACS session with matching
CCSID.