Skip to Content

Changes for page SFTP Known Hosts

Last modified by Danniar Firdausy on 2024/09/18 20:35
From version 22.1
edited by Erik Bakker
on 2022/08/30 15:27
Change comment: There is no comment for this version
To version 25.1
edited by Erik Bakker
on 2023/10/17 11:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -29,7 +29,7 @@
29 29  * Public key should be known to the SFTP (server), so they trust us when we set up the communication
30 30  * A private key comes with a passphrase
31 31  
32 -If you are looking for some introductory reading into certificates, please check this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Securing data traffic.novice-securing-your-data-traffic-what-are-certificates.WebHome||target="blank"]].
32 +If you are looking for some introductory reading into certificates, please check this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Securing Data Traffic.novice-securing-your-data-traffic-what-are-certificates.WebHome||target="blank"]].
33 33  
34 34  As the private key is yours, you can ask a trusted party to generate the key, or you could create it yourself. The latter part happens a lot when connecting to an SFTP. You could use a tool like PuttyGen to achieve this. As a result, you will have a keypair. The private key should be kept safely with you in eMagiz, and you need to share the public key with the SFTP server party. In this microlearning, I will not explain how PuttyGen works in detail. Instead, we will focus on the part in eMagiz. In eMagiz, we need to refer to the key file (linked under Resources), and we need to refer to the password we use to save our key file securely.
35 35  
... ... @@ -41,28 +41,19 @@
41 41  
42 42  Using this setting gives the server the option to verify if the communication request came from eMagiz (or at least from the party that holds the private key of eMagiz). This is an additional security measure to ensure data integrity and quality.
43 43  
44 -== 4. Assignment ==
44 +== 4. Key takeaways ==
45 45  
46 -Check within your project(s) whether an SFTP connection is secured with the help of private key construction.
47 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
48 -
49 -== 5. Key takeaways ==
50 -
51 51  * Private key is unique per client
52 52  * Private key should only be known to the client
53 53  * Public key should be known to the SFTP (server), so they trust us when we set up the communication
54 54  * A private key comes with a passphrase
55 55  
56 -== 6. Suggested Additional Readings ==
51 +== 5. Suggested Additional Readings ==
57 57  
58 58  If you are interested in this topic and want more information, please read the release notes provided by eMagiz. Furthermore, check out these links:
59 59  
60 -* https://docs.spring.io/spring-integration/docs/2.2.6.RELEASE/reference/html/sftp.html#sftp-outbound
61 -* https://docs.spring.io/spring-integration/docs/2.2.6.RELEASE/reference/html/sftp.html#sftp-session-factory
62 -* https://www.2brightsparks.com/resources/articles/sftp-authentication.html
55 +* [[SFTP Outbound>>https://docs.spring.io/spring-integration/docs/2.2.6.RELEASE/reference/html/sftp.html#sftp-outbound||target="blank"]]
56 +* [[SFTP Session Factory>>https://docs.spring.io/spring-integration/docs/2.2.6.RELEASE/reference/html/sftp.html#sftp-session-factory||target="blank"]]
57 +* [[SFTP Authentication>>https://www.2brightsparks.com/resources/articles/sftp-authentication.html||target="blank"]]
63 63  
64 -== 7. Silent demonstration video ==
65 -
66 -As this is a more theoretical microlearning, there is no video.
67 -
68 68  )))((({{toc/}}))){{/container}}{{/container}}