Re: 3rd day on the list, no messages... just wondering if it is a dead or just very quiet list.

Sandip Wadje wrote:

> Hi Bill,
>           seems that very few people are using this list.
>  
>
>  
> Regards,
> Sandip Wadje
> ===========================================
> Assistant Director (Technical) & Officer-In-Charge
> Software Technology Parks of India,Aurangabad.
> Mobile: 9822028312
> Alternate E-mail: [email protected] <mailto:[email protected]>
> ===========================================
>  
>
>
>
>
>
> ____________________________________________________
> <http://www.incredimail.com/redir.asp?ad_id=309&lang=9>  /IncrediMail/ 
> - *Email has finally evolved* - *_Click Here_* 
> <http://www.incredimail.com/redir.asp?ad_id=309&lang=9>

I am getting ready to ask some dreaded questions about generating a self 
signed certificate that does not set off every alarm bell and whistle 
possible upon entry by my friends and partners...

I don't want or care whether they "trust me" per se because of a 
"trusted" certificate.
All WE care about is being able to let them upload ENCRYPTED files to a 
server that stores them in "encrypted" and secured data files...

It's not like we want to process "imf transactions"...
And I am loathe to pay "thawte" money to hold a public key, for me, on a 
system I don't  TRUST... just for the privilege of letting a fellow 
editor, send me an investigative report and keeping it on an encrypted 
file system on a password only system....

As it is, every time one of my partners goes there to down load a file 
we have been working on, they get "this is not a trusted site" and think 
that their files are being stolen... the crazy thing is, I can send them 
to the NON SSL server, and they don't get any messages for anything we 
pass back and forth... but on this system we are wide open...

FWIW... it is a source of irritation for me to have to explain, we don't 
let others have copies of our "public keys" to the server... and if you 
want to send me an encrypted file, you will have to make do... with a 
self signed certificate... and the " we don't trust this" messages from 
the browser...

</endrant>