Neil Nelson wrote:

> Thank you for the VeriSign pages. I quickly looked through

> them, and it seems as though much of their functionality

> overlaps the functionality we are intending for the security

> portion of the IOS.  What comes to mind is that we could

> expand the services offered by the server to customers

> generally and provide standard IOS functions in Jure's

> program to easily utilize the additional services.

>

> At the moment I am trying to figure out how to integrate

> OpenSSL with Jure's program.  I very likely cannot send

> my SSL application portion to him since he is not in the U.S.



1. As an optional component, this encryption function does not require

me to have a copy, however it does require me to have a similar function

that will decrypt your messages.



2. About the design: After your function has read the encrypted Input

from the Registry, it should write the decrypted version to a Registry

key named "HKEY_USERS\Default\Software\VB and VBA Program

Settings\IOS\Forced actions\Add to queue", then write an Answer and a

Result containing a non functional line (something not in IOS language,

for example "!").



The function call should be something like "local-encryption:

Decode,hf56gj2gf2564h3562h5645jh64k25]", make sure that the encoded

message does not contain symbols used by IOS language.



Basicaly, I can make an encryption, that might not be that good, but

more international than SSL and still a little something that will

prevent anyone from simply reading the UDP textual stream.



3. I am onto the theory of how am I going to implent user-verification

(authorificiation or whatever, I don't know how to spell that one),

because it has to be fused to the IOS core if we want it to have the

desired effect. If I implent simple username verification, there will be

nothing preventing someone from using another person's username and if I

add a password, there will be nothing preventing someone from using

another person's password. Ok, that last one is unlikely in an

implementation I have in mind. I will try to implent a link to your

encoding system that would make something like "Require encrypted

password" possible in IOS.



The problem is that if you require to get the username and password

before any other function can be called, the user can't call the

decryptor to send his encrypted password. Then again if only this one is

allowed, the user could simply send whatever orders he has in trough the

encryptor, so no need for username and password entry. If you'd want me

to make a filter that will only let logins to the encryptor, I've got to

tell you that the program is not telepatic to know what in the world is

in the encrypted message headed to the decryptor.



4. I was looking back a bit and I found some ideas of a program, that

could do the upkeep works on a computer automaticaly. The idea is a bit

science-fiction-like, but to tell the truth, I do not see a problem with

making one as a function for Function server. I'll add this one to the

bottom of my priority list.



5. I have been checking out technology a bit. The reason was that I was

interested in the option of using IOS in industry, to support machinery

that hasn't got much processing capacity. For example, wouldn't it be

nice for an owner of a small hidro-powerplant to have all control over

it via his cellphone as he has if he is standing in front of the

powerplant's control panel (current technology only allows the owner to

recieve an SMS in case the power-plant phases out, then he has to visit

it to make any modifications or to restrart it)?



What is my conclusinon? That we've got to be living in stone-age! I

can't belive this, both the hardware and the principles of the

devolopers are far behind anything I ever considered as modern

technology!! Even BlueTooth, the very pin of the nowadays technology, is

just pathetic; sure it is a powerfull piece of hardware, but the

official documentation to devolop software for it is so imposible, that

it is rendered completely useless to most! 



We will not have a problem with pioneering braketroughs here, all the

other devolopers working on this area are still living in stone-age... A

hardware devoloper that dosen't give a damn about the user-friendliness

of his product or a mobile network keeper who's network can be spyed

upon using a simple WW2 radio reciever, well even if I *TRY* I can't get

it worse than it is!!!



--



Don't feel bad about asking/telling me anything, I will always gladly

reply.



Digging for info? Try AI Meta Search:

Http://WWW.AIMetaSearch.Com



GTSC4 -- If nobody else wants to do it, why shouldn't we?(TM)

Meson & GTSC4 are now merged:

Http://WWW.MesonAI.Com

