Dismiss Notice
Join Physics Forums Today!
The friendliest, high quality science and math community on the planet! Everyone who loves science is here!

Help with PGP and RSA for secure FTP transmission

  1. Oct 20, 2014 #1

    TumblingDice

    User Avatar
    Gold Member

    I've been asked to complete a project that requires secure FTP transmission of confidential legal agreements. Despite a healthy background/experience in data communications in the banking industry, time has passed and I've never used PGP or RSA before. NOTE: Everything will be done under Windows and/or IIS. I have a local IIS server for developing/testing, and a public IIS server (if need be) to support the testing phase.

    I need to submit a form to apply for secure connectivity. It's asking for both PGP and RSA public keys that we'll use to download new files

    My #1 "void" is how to generate the keys properly. Number #2 is how to deliver them in a professional manner. I've tried on my own, using Kleopatra for PGP generation, and "PuttyGen" on the RSA side. I'm feeling "lost at sea"...

    My goal is to completely understand before completing a 'perfect' a software solution, yet I'd appreciate a 'recipe' to follow at the moment, hoping to catch up as I go.

    Here is the workflow diagram:
    Secure-FTP.png

    Can anyone help with step-by-step recipes to create both the PGP and RSA keys, and subsequent steps to "do it the right way"...?

    The application form I need to submit is a Word doc with numbered questions to fill in. So - in my response to "Public PGP Key for Data Encryption", should I post the '*.pgp' file to a server and provide a link to it? Or should I just 'paste' the open text of the certificate into the Word doc? (Or maybe both.)

    And how to deliver the same for the RSA side? Can I paste the open text into the Word doc, or does it need to be installed on a server and communicated from there? My local server isn't public - so I can install on the public server if that's the correct way to begin?

    Much TIA!
     
  2. jcsd
  3. Oct 25, 2014 #2
    Thanks for the post! Sorry you aren't generating responses at the moment. Do you have any further information, come to any new conclusions or is it possible to reword the post?
     
  4. Oct 28, 2014 #3

    vela

    User Avatar
    Staff Emeritus
    Science Advisor
    Homework Helper
    Education Advisor

    It looks like you're actually using SSH File Transfer Protocol, which isn't related to traditional FTP and its secure variants. I think your main concern when generating keys is to make sure they're long enough. As far as step-by-step instructions for generating the keys, I'd just google for that info. There are a lot of tutorials on how to do that.

    The easiest way to send the public keys is to simply send the text file containing the key, so pasting into the Word document should be fine. Just make sure you send the public key, not the private one.
     
  5. Oct 28, 2014 #4

    TumblingDice

    User Avatar
    Gold Member

    @Greg Bernhardt - Thanks a bunch for the 'bump'. I swallowed my pride Friday afternoon and called the source... Learned that I did everything the right way to generate keys, and the techies were happy to hear from me to complete setup on their end. I'm going to post more to the thread this week for those that follow. ;)

    @vela - Thank you for responding! Your info is all "spot on". I used Bing (try it sometime) to locate key generators I felt comfortable with. That went well, and I'll post more info for the PGP and RSA solutions I found RSN. Just as you said, all was "text", yet the files had their own unique extensions. I learned this during my "rapid setup" tech contact :), and communicated the info natively by attaching the PGP and ASC files to an email during the phone call.

    All the best!
    TD
     
Know someone interested in this topic? Share this thread via Reddit, Google+, Twitter, or Facebook




Similar Discussions: Help with PGP and RSA for secure FTP transmission
  1. Internet Security (Replies: 1)

  2. Internet security (Replies: 4)

Loading...