Skip to Content

Changes for page PPK Security - SFTP

Last modified by Martijn Woudstra on 2024/01/11 16:43
From version 25.1
edited by Martijn Woudstra
on 2022/11/10 16:38
Change comment: There is no comment for this version
To version 27.1
edited by Martijn Woudstra
on 2024/01/11 16:43
Change comment: Imported from XAR

Summary

Details

Page properties
Content
... ... @@ -15,7 +15,7 @@
15 15  
16 16  === 3.1 Reproduction ===
17 17  
18 -To reproduce the issue we build a comparable setup in a different eMagiz model using a ppk file (similar to the one used at the client) we generated ourselves and tried to connect to our own SFTP. As a result we got an “invalid private key” exception back. This means that the generated ppk is too new for the library that is used within eMagiz (https://stackoverflow.com/questions/53134212/invalid-privatekey-when-using-jsch). As a remedy we changed the ppk to a pem as detailed in one of the answers of this question. As a result we got an “Auth cancel” error which was to be expected as our ppk was generated by ourselves and the SFTP we were trying to connect to was not aware of this.
18 +To reproduce the issue we build a comparable setup in a different eMagiz model using a ppk file (similar to the one used at the client) we generated ourselves and tried to connect to our own SFTP. As a result we got an “invalid private key” exception back. This means that the generated ppk is too new for the library that is used within eMagiz ([[Invalid Private Key>>https://stackoverflow.com/questions/53134212/invalid-privatekey-when-using-jsch||target="blank"]]). As a remedy we changed the ppk to a pem as detailed in one of the answers of this question. As a result we got an “Auth cancel” error which was to be expected as our ppk was generated by ourselves and the SFTP we were trying to connect to was not aware of this.
19 19  
20 20  === 3.2 Analysis ===
21 21