Bugzilla

I installed mkcert using the "linuxbrew" method and made the certificate and key file for localhost, 127.0.0.1 and ::1. Then built your server using "cargo build". I then run the server like this:
```
response-injection-release]$ target/debug/response-injection ~/.linuxbrew/localhost+2.pem ~/.linuxbrew/localhost+2-key.pem
```
In tb I create the account but don't know what username and password I should use. Otherwise it seems to work. I see the STARTTLS command and  response and the alert popup occurs. It tries to use "login" authentication and asks for password and I give it my usual user password and it fails and nothing more happens. Should I be able to complete the login?
(I'm on fedora 31 linux.)

I installed mkcert using the "linuxbrew" method and made the certificate and key file for localhost, 127.0.0.1 and ::1. Then built your server using "cargo build". I then run the server like this:
```
response-injection-release]$ target/debug/response-injection ~/.linuxbrew/localhost+2.pem ~/.linuxbrew/localhost+2-key.pem
```
In tb I create the account but don't know what username and password I should use. Otherwise it seems to work. I see the STARTTLS command and  response and the alert popup occurs. It tries to use "login" authentication and asks for password and I give it my usual user password and it fails and nothing more happens. Should I be able to complete the login?
(I'm on fedora 31 linux.)

***Edit:*** I see this in the server console:

IMAP: 127.0.0.1:57544 --> 127.0.0.1:10143
S: * OK [CAPABILITY IMAP4REV1 STARTTLS LOGINDISABLED]\r\n
C: 1 STARTTLS\r\n
S: 1 OK start TLS now\r\n* OK [ALERT] This is *plaintext*, which should not have been interpreted. We can inject more plaintext and e.g. already answer Thunderbird\'s upcoming capability command.\r\n2 OK [CAPABILITY IMAP4REV1 AUTH=X1337METHOD]\r\n4 OK login seems legit, I guess?\r\n
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: InvalidData, error: AlertReceived(UnknownCA) }', src/libcore/result.rs:1188:5

I suppose the panic means I don't have somthing set up right?

I installed mkcert using the "linuxbrew" method and made the certificate and key file for localhost, 127.0.0.1 and ::1. Then built your server using "cargo build". I then run the server like this:
```
response-injection-release]$ target/debug/response-injection ~/.linuxbrew/localhost+2.pem ~/.linuxbrew/localhost+2-key.pem
```
In tb I create the account but don't know what username and password I should use. Otherwise it seems to work. I see the STARTTLS command and  response and the alert popup occurs. It tries to use "login" authentication and asks for password and I give it my usual user password and it fails and nothing more happens. Should I be able to complete the login?
(I'm on fedora 31 linux.)

***Edit:*** I see this in the server console:

IMAP: 127.0.0.1:57544 --> 127.0.0.1:10143
S: * OK [CAPABILITY IMAP4REV1 STARTTLS LOGINDISABLED]\r\n
C: 1 STARTTLS\r\n
S: 1 OK start TLS now\r\n* OK [ALERT] This is *plaintext*, which should not have been interpreted. We can inject more plaintext and e.g. already answer Thunderbird\'s upcoming capability command.\r\n2 OK [CAPABILITY IMAP4REV1 AUTH=X1337METHOD]\r\n4 OK login seems legit, I guess?\r\n
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: InvalidData, error: AlertReceived(UnknownCA) }', src/libcore/result.rs:1188:5

I suppose the panic means I don't have somthing set up right?

Edit2: Had to import ~/.local/share/mkcert/rootCA-key.pem. Now I see:

IMAP: 127.0.0.1:57636 --> 127.0.0.1:10143
S: * OK [CAPABILITY IMAP4REV1 STARTTLS LOGINDISABLED]\r\n
C: 1 STARTTLS\r\n
S: 1 OK start TLS now\r\n* OK [ALERT] This is *plaintext*, which should not have been interpreted. We can inject more plaintext and e.g. already answer Thunderbird\'s upcoming capability command.\r\n2 OK [CAPABILITY IMAP4REV1 AUTH=X1337METHOD]\r\n4 OK login seems legit, I guess?\r\n
C: 2 capability\r\n
C: 4 login \"gene@127.0.0.1\" \"mypassword\"\r\n
C: 5 capability\r\n
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: ConnectionAborted, error: "CloseNotify alert received" }', src/libcore/result.rs:1188:5

At least now tb tries to send password but not sure why "capability" is sent twice with no response and then the server still seems to give up and no response to login.