News for hackers. Stuff that matters.
Re:Poste.io – Complete Mail Server by anaganisk on Wednesday February 22, 2023 @11:27PM (#34906760)
At least they are hashing and not storing encrypted passwords. But even a baby framework with may 10-20 users using has switched to bcrypt, etc. Im not sure why they're boasting about SHA512. But I am a little lost on the RFC thing. Could you enlighten me. I thought they were standard ports for legacy,TLS, and SSL ports.
Re:Poste.io – Complete Mail Server by imp0cat on Thursday February 23, 2023 @01:52AM (#34907598)
tldr; 465 is obsolete,you should not use it; 25 is for relaying mail between servers; 587 is the default mail submission port today.
Re:Poste.io – Complete Mail Server by smorrebrod on Thursday February 23, 2023 @02:53AM (#34908011)
Isn't 465 safer since 587 uses STARTTLS and STARTTLS can be downgraded?
Re:Poste.io – Complete Mail Server by justsomehnguy on Thursday February 23, 2023 @03:00AM (#34908048)
> since 587 uses STARTTLS and STARTTLS

Technically yes, but for the last decade I've seen only one instance where 587 was explicitly STARTTLS (Fastmail), everyone else just running TLS on it.

Re:Poste.io – Complete Mail Server by smorrebrod on Thursday February 23, 2023 @03:48AM (#34908343)
How can I check if a connection is TLS or STARTTLS?
Re:Poste.io – Complete Mail Server by imp0cat on Thursday February 23, 2023 @03:57AM (#34908398)
Connect to the smtp server and issue `EHLO something` command, then check if STARTTLS is mentioned in the server response.
Re:Poste.io – Complete Mail Server by smorrebrod on Thursday February 23, 2023 @04:28AM (#34908573)
Thanks!
Re:Poste.io – Complete Mail Server by justsomehnguy on Thursday February 23, 2023 @05:01AM (#34908713)
Minor nitpicks:

a) you need a plain-text aka telnet client for this

b) if you receive a valid, human-readable text then it means what you are not on TLS for sure

c) if B succeeds that doesn't means what that SMTP server support STARTTLS, you should check options and try to initite it , eg:

        220 smtp.fastmail.com ESMTP ready
    ->  EHLO just.testing.things
        250-smtp.fastmail.com
        250-PIPELINING
        250-SIZE 71000000
        250-ENHANCEDSTATUSCODES
        250-8BITMIME
    !!  250 STARTTLS
    ->  STARTTLS
        220 2.0.0 Start TLS
Re:Poste.io – Complete Mail Server by imp0cat on Friday February 24, 2023 @02:18AM (#34921840)
Right, I guess you could also use openssl's s_client like this:

  openssl s_client -starttls smtp -connect smtp.gmail.com:587
  openssl s_client -connect smtp.gmail.com:465
Re:Poste.io – Complete Mail Server by pas on Thursday February 23, 2023 @03:10PM (#34915801)
smtp.gmail.com:587 is still STARTTLS.
Re:Poste.io – Complete Mail Server by account42 on Friday February 24, 2023 @07:30AM (#34923807)
STARTTLS is a protocol. Allowing unencrypted connections is a policy. One does not imply the other.
Re:Poste.io – Complete Mail Server by nona on Thursday February 23, 2023 @05:11AM (#34908769)
Re:Poste.io – Complete Mail Server by imp0cat on Friday February 24, 2023 @02:10AM (#34921792)
As the other commenter pointed out, you are right, it once was, but that is no longer the case.
Re:Poste.io – Complete Mail Server by Avamander on Thursday February 23, 2023 @08:54AM (#34910582)
No, it is not obsolete, quite contrary actually. See RFC8314.

The implicit TLS submission port got deprecated for a brief time, but it's no longer deprecated.

Explicit TLS is a terrible idea and for that reason it's recommended to provide implicit TLS (submissions).

Re:Poste.io – Complete Mail Server by imp0cat on Friday February 24, 2023 @02:09AM (#34921786)
Hey! Thanks for the clarification, looks like an exception was made specifically for smtp. And after reading their reasoning, it does make sense.

Server operators should (and do) provide both 486 and 587 in order to maximize the amount of secure connections to their servers.