From: "Geo." 

"Adam Flinton"  wrote in message
news:3ea9735a$1{at}w3.nls.net...

> I don't think the gov (any gov) can "order the tide to back out". I
> think the same applies to OSS & to OSS security. e.g. imagine you have
> some bright spark maths person in say Ukraine or Russia or India or
> anywhere outside of the US. There is a fairly high % chance that his
> encryption algorithm is going to go OSS & how much control do gov's have
> over that? Security is being driven by bigger $'es than govs can chuck
> about i.e. by the business world & the generic "computer user".

Well if he goes OSS then the proprietary people can see how he's doing
something and that helps them too?

> Can be but IMHO they will have some sort of updateable code block
> otherwise one good hack & the lot is rendered null & void. If you have a
> chip which checks all "content" & is updateable it
becomes a natural
> target for spooks.

Fine but a trusted environment works to stop them from updating anything.

Geo.

--- BBBS/NT v4.01 Flag-4