Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6950971
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T14:09:35+00:00 2026-05-27T14:09:35+00:00

What are the security implications of storing your keys ( app_cert.pem , app_key.pem ,

  • 0

What are the security implications of storing your keys (app_cert.pem,app_key.pem, paypal.pem), which are used to encrypt/sign your paypal transactions, in VCS? I’m thinking that someone who has the certificate and my database primary key will be able to mark a purchase as paid. That’s the worst that can happen, right?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T14:09:35+00:00Added an answer on May 27, 2026 at 2:09 pm

    The biggest danger is in who has access to the source control. If the developers that have access to the source control are already allowed to have acccess to the keys, then there is no additional risk as long as the source control is locked down so that only authorized users have access.

    If you allow anonymous read access to the repository, then someone else can get your keys, which may be helpful to a dedicated attacker. Perhaps they’ll know how to do something with it that we wouldn’t think of.

    Never underestimate the ingenuity of someone who has the skill and the lack of scruples, and the motivation of an easy payday.

    Personally, I wouldn’t put them in source control. I’d protect them as if they were my own SSN and bank info.

    Even if your repo is locked down tight now, you don’t know what will change in the future. It would be too easy for some future developer to start collaborating with an outside vendor, for example, and grant read-only access, not thinking that they’re exposing such sensitive info.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Maybe this isn't possible due to Security implications... I have a Deployment Package created
I'm not sure about the security implications of this and if its privileged info.
Putting aside the security implications of running a script someone gives me, how can
Are there any security implications to making an HTTPS/SSL GET operation with sensitive data
What are the security implications for hosting signed jars on the internet? As I
What are the security implications of websites accessing database views instead of using stored
I'm currently reviewing the security implications of various warnings in a large Java EE
For security reasons, several articles recommend do not cache pages. So I usually put
For security purposes, I want to stop the users from being able to view
The security policy at our client's production environment requires that we use separate connection

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.