How to transfer text information safely?

Question

Information Security

Soon I will start cooperation with the development studio. I act as a customer, the studio will carry out work on back-end development. The question is how to most safely transfer access to the domain, hosting and other services that their developer will work with. It is clear that after the completion of the work, all accesses will change, but I would like to know how this happens with other guys?

Answer 1

As an option, it is possible through mail in encrypted form. Let's say with the help of Enigmail.

Answer 2

Ill messenger with end-to-end encryption: Telegramm, WhatsApp.

Answer 3

If the option is without unnecessary troubles, then it is enough to share the document from Google Drive, indicating the email addresses of the recipients.
If supposedly "military" secrecy is needed, then using PGP to encrypt it and send it at least by regular mail.

Answer 4

What do you want to protect against. From data theft on the way from you to the developer? Passwords in a text file, a file in an encrypted archive. You send the archive by mail, the password from it is sent by SMS to the developer.

Answer 5

When I worked for a government office, before sending a letter (I don’t remember in Word anymore) they encrypted this file with the CryptoPro program, and the decryption key was already on the other side, you can transfer it as mentioned earlier by sms (messenger) or lay it out the key on the site and throw off a link with a description, a file hosting service with anything at least by Russian mail

Answer 6

If in Windows, then the easiest way is RAR with a password of twenty characters on the full set (a-zA-Z0-9 and all icons) or AxCrypt (should be on both sides).
If in linux - openssl enc / openssl dec with the same password
Or anywhere - a letter encrypted with a personal certificate (certificates must first be issued and exchanged, your own CA is enough for this - you don’t care about the trust of the whole world)

Answer 7

All access except passwords can be sent in clear text.
Also, you can encrypt in the archive, BUT! the main thing NOT PASSWORD ACCESS TO THE SERVER!
We set the password to the server long and such that it does not attract the attention of one of the parts, and we break it into two parts.
Password example: 4764_S989854SSL Divide
: "4764_S989854" and "SSL".
Then we send both halves through two different communication channels, telling how to assemble.
It's better to use chat with e2ee or end-to -end encryption .
I advise you to read how it works here .