2 edited title
| link

Reading HTTPSencrypted data before sent to remote server

source | link

Reading HTTPS data before sent to remote server

I'm developing a mobile app (Android only for now) to provide a disposable e-mail service to users. Users will be given temporary e-mail addresses so they can receive and read e-mails for a certain period of time, then accounts are completely destroyed.

In this architecture, I'm not interested in users knowing the passwords for their e-mail accounts, because they could log-in via a common client and send mails or even spam (currently I want to allow only incoming e-mails, not outgoing).

My idea is to generate a pseudo-random password inside the app each time the user wants to create a disposable e-mail, send it through a HTTPS POST request to the remote server so the account can be created, and then allow the user log into the account using a small client via IMAPS.

I know both HTTPS and IMAPS should provide enough security as far as the client <-> server data goes, but I'm concerned about the possibility users could break the code (or introduce a device before their router so the HTTPS mailbox creation request might be read before sent, or alike) and somehow get the password for the temporary account while the account still exists.

How real is this situation? If users can get the passwords with the above schema, is there a way I can achieve my purpose in a secure way?