RE: My first time outside the default activation group

Can't help on the activation part, but assuming the MD5 source is for a MD5 hash I want to point out that MD5 is not an 'encryption' it's a hash. What's the difference? You can't UNhash something, you can UNencrypt (decrypt) something.

For passwords you do typically use a hash, and you simply hash the user supplied password at login and if the hashs match then you let them in. but you will loose password recovery for example, as there's no way to get back their password.

You probably knew all this but since you said you wanted to use MD5 to 'encrypt' I thought i'd point it out.

-Walden

--
Sent from my wireless device.

-----Original Message-----
From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
Sent: 16 October, 2008 05:25
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: My first time outside the default activation group

Hi all,

Just been given an RPG source called MD5 and told to call it to encrypt all the passwords of our internet users. I don't know exactly where this source comes from but you can find it in the archives and elsewhere on the net.

It says to compile with ACTGRP(QILE) and BNDDIR(QC2LE)

We are a shop where everything is compiled with ACTGRP(*CALLER) and there are as yet no SRVPGM to be found. So, I believe that effectively, everything will run in the DFTACTGRP.

Now as MD5 has a stack of SRVPGM, I understand that strange things might happen between calls if I compile it with ACTGRP(*CALLER).

My program will read a userID file, and for each user call MD5 for the encryption.

If my program starts in DFTACTGRP, how should I handle things between each call to MD5?
Why compile MD5 in QILE ?
Couldn't I create a module from MD5, bind it to my program and compile my program in a named activation group that I would destroy when all my passwords are encypted?


Thanks.