Update Linux secure log to show escalation to root not as the user but as its RSA Cert IDdenyhosts is...

In the twin paradox does the returning twin also come back permanently length contracted flatter than the twin on earth?

How can I communicate feelings to players without impacting their agency?

Where does the upgrade to macOS Catalina move root "/" directory files?

Advisor asked for my entire slide presentation so she could give the presentation at an international conference

Why is technology bad for children?

How can I check the implementation of a builtin function?

Moonlight bright enough to see by

What's that funny "illo" I keep hearing in Southern Spain?

Christmas party at employers home

Which CentOS 7 package provides the "boot" manpage?

Symbolise polygon outline where it doesn't coincide with other feature using geometry generator in QGIS?

Demod as a neologism

Why are second inversion triads considered less consonant than first inversion triads?

How should I understand FPGA architecture?

Why is Trump releasing or not of his taxes such a big deal?

Limiting sensor input voltage without biasing measurement

Word for 'most late'

Does a restocking fee still qualify as a business expense?

How do I get my boyfriend to remove pictures of his ex girlfriend hanging in his apartment?

How to extract *.tgz.part-*?

Milk instead of water in bread

Why do these two ways of understanding constant acceleration give different results?

I am often given, occasionally stolen, rarely sold, and never borrowed

What is the gold linker?



Update Linux secure log to show escalation to root not as the user but as its RSA Cert ID


denyhosts is blocking existing users from logging in from unknown (new) IP addressesSSH via cert-authoritycan't login in new user via ssh 'server refused our key'log or restrict the source user of ssh loginSSH Configuration Help / Can't tunnel






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{
margin-bottom:0;
}








0

















I looked all over Google.com but I couldn't find any answers. I am hoping someone could help me here.



Background Info:
We use a Certificate Authority Server that signs our engineers Public/Private key and issues them a certificate. Our engineers will then use that certificate to SSH into the instances. The Certificate Authority server's public key is distrubuted on all our EC2 instances and SSHD conf is updated to trust a CA and its public key.



All our engineers' SSH as ec2-user and Linux secure logs record the following entry when an engineer SSHs into an instance



Oct  9 20:30:24 awesomelinuxserver sshd[5079]: Accepted publickey for ec2-user from 192.168.7.99 port 12118 ssh2: RSA-CERT ID john.doe (serial 6666669999985847) CA RSA SHA256:uef8+ggsgkJ6kC2Yfadfa+TbZadf28AFY


Problem:
When an engineer su to root the following log is recorded in the secure log:



Oct  9 22:28:35 awesomelinuxserver su: pam_unix(su:session): session opened for user root by ec2-user(uid=0)


Question:
How do I tailor the secure log to record the su escalation as the user's RSA-CERT ID rather than the user? So instead of saying su session opened to root by ec2-user, it should say su session opened to root by john.doe. Has anyone done this before?










share|improve this question







New contributor



Doug is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.































    0

















    I looked all over Google.com but I couldn't find any answers. I am hoping someone could help me here.



    Background Info:
    We use a Certificate Authority Server that signs our engineers Public/Private key and issues them a certificate. Our engineers will then use that certificate to SSH into the instances. The Certificate Authority server's public key is distrubuted on all our EC2 instances and SSHD conf is updated to trust a CA and its public key.



    All our engineers' SSH as ec2-user and Linux secure logs record the following entry when an engineer SSHs into an instance



    Oct  9 20:30:24 awesomelinuxserver sshd[5079]: Accepted publickey for ec2-user from 192.168.7.99 port 12118 ssh2: RSA-CERT ID john.doe (serial 6666669999985847) CA RSA SHA256:uef8+ggsgkJ6kC2Yfadfa+TbZadf28AFY


    Problem:
    When an engineer su to root the following log is recorded in the secure log:



    Oct  9 22:28:35 awesomelinuxserver su: pam_unix(su:session): session opened for user root by ec2-user(uid=0)


    Question:
    How do I tailor the secure log to record the su escalation as the user's RSA-CERT ID rather than the user? So instead of saying su session opened to root by ec2-user, it should say su session opened to root by john.doe. Has anyone done this before?










    share|improve this question







    New contributor



    Doug is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.



























      0












      0








      0








      I looked all over Google.com but I couldn't find any answers. I am hoping someone could help me here.



      Background Info:
      We use a Certificate Authority Server that signs our engineers Public/Private key and issues them a certificate. Our engineers will then use that certificate to SSH into the instances. The Certificate Authority server's public key is distrubuted on all our EC2 instances and SSHD conf is updated to trust a CA and its public key.



      All our engineers' SSH as ec2-user and Linux secure logs record the following entry when an engineer SSHs into an instance



      Oct  9 20:30:24 awesomelinuxserver sshd[5079]: Accepted publickey for ec2-user from 192.168.7.99 port 12118 ssh2: RSA-CERT ID john.doe (serial 6666669999985847) CA RSA SHA256:uef8+ggsgkJ6kC2Yfadfa+TbZadf28AFY


      Problem:
      When an engineer su to root the following log is recorded in the secure log:



      Oct  9 22:28:35 awesomelinuxserver su: pam_unix(su:session): session opened for user root by ec2-user(uid=0)


      Question:
      How do I tailor the secure log to record the su escalation as the user's RSA-CERT ID rather than the user? So instead of saying su session opened to root by ec2-user, it should say su session opened to root by john.doe. Has anyone done this before?










      share|improve this question







      New contributor



      Doug is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I looked all over Google.com but I couldn't find any answers. I am hoping someone could help me here.



      Background Info:
      We use a Certificate Authority Server that signs our engineers Public/Private key and issues them a certificate. Our engineers will then use that certificate to SSH into the instances. The Certificate Authority server's public key is distrubuted on all our EC2 instances and SSHD conf is updated to trust a CA and its public key.



      All our engineers' SSH as ec2-user and Linux secure logs record the following entry when an engineer SSHs into an instance



      Oct  9 20:30:24 awesomelinuxserver sshd[5079]: Accepted publickey for ec2-user from 192.168.7.99 port 12118 ssh2: RSA-CERT ID john.doe (serial 6666669999985847) CA RSA SHA256:uef8+ggsgkJ6kC2Yfadfa+TbZadf28AFY


      Problem:
      When an engineer su to root the following log is recorded in the secure log:



      Oct  9 22:28:35 awesomelinuxserver su: pam_unix(su:session): session opened for user root by ec2-user(uid=0)


      Question:
      How do I tailor the secure log to record the su escalation as the user's RSA-CERT ID rather than the user? So instead of saying su session opened to root by ec2-user, it should say su session opened to root by john.doe. Has anyone done this before?







      ssh rhel sshd certificates






      share|improve this question







      New contributor



      Doug is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor



      Doug is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share|improve this question




      share|improve this question






      New contributor



      Doug is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      asked 1 hour ago









      DougDoug

      11 bronze badge




      11 bronze badge




      New contributor



      Doug is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




      New contributor




      Doug is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.



























          0






          active

          oldest

          votes













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });







          Doug is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded
















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f546023%2fupdate-linux-secure-log-to-show-escalation-to-root-not-as-the-user-but-as-its-rs%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown


























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          Doug is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded

















          Doug is a new contributor. Be nice, and check out our Code of Conduct.













          Doug is a new contributor. Be nice, and check out our Code of Conduct.












          Doug is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f546023%2fupdate-linux-secure-log-to-show-escalation-to-root-not-as-the-user-but-as-its-rs%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown









          Popular posts from this blog

          Hudson River Historic District Contents Geography History The district today Aesthetics Cultural...

          The number designs the writing. Feandra Aversely Definition: The act of ingrafting a sprig or shoot of one...

          Ayherre Geografie Demografie Externe links Navigatiemenu43° 23′ NB, 1° 15′ WL43° 23′ NB, 1°...