433
Looks like gitlab now requires account verification for new accounts in addition to email. Either phone number or credit card.
This applies both to accounts created with a working email or by logging in using your github account. You can't even verify your email until you go through step 1.
I don't know when this started, but at least for the last month or two judging from these posts in the forums.
- https://forum.gitlab.com/t/how-to-create-an-account-without-telephone-number-if-an-non-activated-account-has-already-been-created-with-the-same-e-mail-address-that-demands-a-phone-number/93675/2
- https://forum.gitlab.com/t/phone-verification-sms-not-received-unable-to-login-and-register/92202
- https://forum.gitlab.com/t/how-to-create-an-account-without-telephone-number-if-an-non-activated-account-has-already-been-created-with-the-same-e-mail-address-that-demands-a-phone-number/93675/2
Fun fact: I don't even want to host on gitlab, I just wanted to report bugs in some projects. So I'm locked out.
Why isn't FTP secure
because it hasn't got an S in it
It's unencrypted, your ISP / Starbucks wifi can read all the files you send. Use SFTP instead.
or FTPS
SFTP is a 'part' of SSH, FTPS is FTP but encrypted.
Yes, SFTP > FTP-S.
Yeah, I think you need to go out of your way to try to use ftps. When people say ftp they generally mean SFTP.
Especially when it comes to gateway configuration.
Not just read but modify even.