Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Multiple Params for Deferred CA


4 replies to this topic

hteichert

hteichert
  • Members
  • 158 posts

Posted 21 June 2002 - 09:26

Normally it's no problem to give multiple parameters to a deferred CA by using the property CustomActionData and split the params by using a special character as delimiter (I think most of the people use ";").

But:
I have to transfer several parameters to a deferred CA and one of them (a password) might contain everything (like " , ; ? ....).
How is it possible to split all these params without destroying the one, which might contain everything? Any idea?
h.teichert-ott

Irina

Irina
  • Members
  • 227 posts

Posted 27 June 2002 - 21:34

Hi,
If you have only one parameters such this (all chars are possible), then set it at first and put it in any signs, like this:
CustomActionData      $Password$;Par2;Par3
Then find a first occurence of $ from the back, so you can separate this parameters from others. Use usually splitting for others.
Hope it helps.
Irina Shirinsky
Software Engineer, Heroix Corporation
http://www.heroix.com

hteichert

hteichert
  • Members
  • 158 posts

Posted 28 June 2002 - 14:23

Thanks, Irina. I had the same idea, but using the PWD in the end and doing the work just vice versa.

But:
What can be done if there are more than one "unrestricted" parameters to be transferred? Like logging on as user1 with pwd1 to create another user2/pwd2??

OK, one idea is to use uuencode/decode to transfer the data, but isn't there a simpler way to do it?
h.teichert-ott

rjtonnis

rjtonnis
  • Members
  • 8 posts

Posted 28 June 2002 - 15:34

You could try this:
Write a CA that is not deferred and have it read the properties directly and transfer them to the registry.  Then have your Deferred CA read (and delete) the parameters from the registry.
Rob

hteichert

hteichert
  • Members
  • 158 posts

Posted 28 June 2002 - 15:49

Good idea at first, but there is a security problem.

If the data transferred are passwords, then they could be read by somebody else - for example when the setup crashes just in the middle of the installation (power fail, another application running wild, ...). It's never a good idea to store passwords unencrypted.
h.teichert-ott