unlock kwallet at login












4















before plasma 5 I had my kwallet unlocked at login and it worked well (same password for kwallet as for my session).



Now, with plasma 5, it does not work anymore, I think I'm not far from working this out, but I don't know what to do next.



Here is my setup, in ~/.config/plasma-workspace/env/ssh-agent.sh :



#!/bin/bash
export SSH_ASKPASS=/usr/bin/ksshaskpass
eval $(ssh-agent)
/usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite


Note that I load 2 keys whith ssh-add. After login in, I have to unlock my wallet 2 times before the desktop shows up.



Anybody see What is going wrong ?



Thanks a lot.










share|improve this question























  • Here is an idea : maybe it's because the ksshaskpass is launched too early in the connection process. I'l look at this.

    – skizo
    Jun 2 '15 at 7:02











  • I have the same problem. I only have to enter my password once for kwallet, though (so, twice in total: once for login, once for kwallet) (Kubuntu 15.10) (sddm seems to talk to pam_kwallet.so somehow, according to syslog)

    – Magnus Hoff
    Nov 10 '15 at 10:31













  • In Kubuntu 15.10, there are more services using the kwallet5 framework (maybe this sentence is a bit inacurate ...). But the problem persists. Anyway, I switched back to XFCE, because of the sum of little annoyances in KDE. I miss some features though.

    – skizo
    Nov 18 '15 at 13:28













  • any solution yet? I have the same problem and I realized it is because of sddm not plasma. for example: with gdm kwallet is unlocked before the profile get's loaded.

    – iRaS
    Jan 28 at 6:48
















4















before plasma 5 I had my kwallet unlocked at login and it worked well (same password for kwallet as for my session).



Now, with plasma 5, it does not work anymore, I think I'm not far from working this out, but I don't know what to do next.



Here is my setup, in ~/.config/plasma-workspace/env/ssh-agent.sh :



#!/bin/bash
export SSH_ASKPASS=/usr/bin/ksshaskpass
eval $(ssh-agent)
/usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite


Note that I load 2 keys whith ssh-add. After login in, I have to unlock my wallet 2 times before the desktop shows up.



Anybody see What is going wrong ?



Thanks a lot.










share|improve this question























  • Here is an idea : maybe it's because the ksshaskpass is launched too early in the connection process. I'l look at this.

    – skizo
    Jun 2 '15 at 7:02











  • I have the same problem. I only have to enter my password once for kwallet, though (so, twice in total: once for login, once for kwallet) (Kubuntu 15.10) (sddm seems to talk to pam_kwallet.so somehow, according to syslog)

    – Magnus Hoff
    Nov 10 '15 at 10:31













  • In Kubuntu 15.10, there are more services using the kwallet5 framework (maybe this sentence is a bit inacurate ...). But the problem persists. Anyway, I switched back to XFCE, because of the sum of little annoyances in KDE. I miss some features though.

    – skizo
    Nov 18 '15 at 13:28













  • any solution yet? I have the same problem and I realized it is because of sddm not plasma. for example: with gdm kwallet is unlocked before the profile get's loaded.

    – iRaS
    Jan 28 at 6:48














4












4








4


1






before plasma 5 I had my kwallet unlocked at login and it worked well (same password for kwallet as for my session).



Now, with plasma 5, it does not work anymore, I think I'm not far from working this out, but I don't know what to do next.



Here is my setup, in ~/.config/plasma-workspace/env/ssh-agent.sh :



#!/bin/bash
export SSH_ASKPASS=/usr/bin/ksshaskpass
eval $(ssh-agent)
/usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite


Note that I load 2 keys whith ssh-add. After login in, I have to unlock my wallet 2 times before the desktop shows up.



Anybody see What is going wrong ?



Thanks a lot.










share|improve this question














before plasma 5 I had my kwallet unlocked at login and it worked well (same password for kwallet as for my session).



Now, with plasma 5, it does not work anymore, I think I'm not far from working this out, but I don't know what to do next.



Here is my setup, in ~/.config/plasma-workspace/env/ssh-agent.sh :



#!/bin/bash
export SSH_ASKPASS=/usr/bin/ksshaskpass
eval $(ssh-agent)
/usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite


Note that I load 2 keys whith ssh-add. After login in, I have to unlock my wallet 2 times before the desktop shows up.



Anybody see What is going wrong ?



Thanks a lot.







ssh login kde plasma-5 kwallet






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 21 '15 at 8:06









skizoskizo

1913




1913













  • Here is an idea : maybe it's because the ksshaskpass is launched too early in the connection process. I'l look at this.

    – skizo
    Jun 2 '15 at 7:02











  • I have the same problem. I only have to enter my password once for kwallet, though (so, twice in total: once for login, once for kwallet) (Kubuntu 15.10) (sddm seems to talk to pam_kwallet.so somehow, according to syslog)

    – Magnus Hoff
    Nov 10 '15 at 10:31













  • In Kubuntu 15.10, there are more services using the kwallet5 framework (maybe this sentence is a bit inacurate ...). But the problem persists. Anyway, I switched back to XFCE, because of the sum of little annoyances in KDE. I miss some features though.

    – skizo
    Nov 18 '15 at 13:28













  • any solution yet? I have the same problem and I realized it is because of sddm not plasma. for example: with gdm kwallet is unlocked before the profile get's loaded.

    – iRaS
    Jan 28 at 6:48



















  • Here is an idea : maybe it's because the ksshaskpass is launched too early in the connection process. I'l look at this.

    – skizo
    Jun 2 '15 at 7:02











  • I have the same problem. I only have to enter my password once for kwallet, though (so, twice in total: once for login, once for kwallet) (Kubuntu 15.10) (sddm seems to talk to pam_kwallet.so somehow, according to syslog)

    – Magnus Hoff
    Nov 10 '15 at 10:31













  • In Kubuntu 15.10, there are more services using the kwallet5 framework (maybe this sentence is a bit inacurate ...). But the problem persists. Anyway, I switched back to XFCE, because of the sum of little annoyances in KDE. I miss some features though.

    – skizo
    Nov 18 '15 at 13:28













  • any solution yet? I have the same problem and I realized it is because of sddm not plasma. for example: with gdm kwallet is unlocked before the profile get's loaded.

    – iRaS
    Jan 28 at 6:48

















Here is an idea : maybe it's because the ksshaskpass is launched too early in the connection process. I'l look at this.

– skizo
Jun 2 '15 at 7:02





Here is an idea : maybe it's because the ksshaskpass is launched too early in the connection process. I'l look at this.

– skizo
Jun 2 '15 at 7:02













I have the same problem. I only have to enter my password once for kwallet, though (so, twice in total: once for login, once for kwallet) (Kubuntu 15.10) (sddm seems to talk to pam_kwallet.so somehow, according to syslog)

– Magnus Hoff
Nov 10 '15 at 10:31







I have the same problem. I only have to enter my password once for kwallet, though (so, twice in total: once for login, once for kwallet) (Kubuntu 15.10) (sddm seems to talk to pam_kwallet.so somehow, according to syslog)

– Magnus Hoff
Nov 10 '15 at 10:31















In Kubuntu 15.10, there are more services using the kwallet5 framework (maybe this sentence is a bit inacurate ...). But the problem persists. Anyway, I switched back to XFCE, because of the sum of little annoyances in KDE. I miss some features though.

– skizo
Nov 18 '15 at 13:28







In Kubuntu 15.10, there are more services using the kwallet5 framework (maybe this sentence is a bit inacurate ...). But the problem persists. Anyway, I switched back to XFCE, because of the sum of little annoyances in KDE. I miss some features though.

– skizo
Nov 18 '15 at 13:28















any solution yet? I have the same problem and I realized it is because of sddm not plasma. for example: with gdm kwallet is unlocked before the profile get's loaded.

– iRaS
Jan 28 at 6:48





any solution yet? I have the same problem and I realized it is because of sddm not plasma. for example: with gdm kwallet is unlocked before the profile get's loaded.

– iRaS
Jan 28 at 6:48










1 Answer
1






active

oldest

votes


















0














I have a workaround that I don't want to use anymore maybe it helps someone.



Add the following if statement around your ssh-add command:



#!/bin/bash
export SSH_ASKPASS=/usr/bin/ksshaskpass
eval $(ssh-agent)

if pstree -s -p $$ | grep Xsession; then
exit
fi

/usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite


Explanation: When you start a terminal the parent process is not a Xsession and therefore the ssh-add command is executed. At this time the kwallet is already unlocked and it does not ask for the passphrases of the ssh keys.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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/3.0/"u003ecc by-sa 3.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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f626423%2funlock-kwallet-at-login%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I have a workaround that I don't want to use anymore maybe it helps someone.



    Add the following if statement around your ssh-add command:



    #!/bin/bash
    export SSH_ASKPASS=/usr/bin/ksshaskpass
    eval $(ssh-agent)

    if pstree -s -p $$ | grep Xsession; then
    exit
    fi

    /usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite


    Explanation: When you start a terminal the parent process is not a Xsession and therefore the ssh-add command is executed. At this time the kwallet is already unlocked and it does not ask for the passphrases of the ssh keys.






    share|improve this answer




























      0














      I have a workaround that I don't want to use anymore maybe it helps someone.



      Add the following if statement around your ssh-add command:



      #!/bin/bash
      export SSH_ASKPASS=/usr/bin/ksshaskpass
      eval $(ssh-agent)

      if pstree -s -p $$ | grep Xsession; then
      exit
      fi

      /usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite


      Explanation: When you start a terminal the parent process is not a Xsession and therefore the ssh-add command is executed. At this time the kwallet is already unlocked and it does not ask for the passphrases of the ssh keys.






      share|improve this answer


























        0












        0








        0







        I have a workaround that I don't want to use anymore maybe it helps someone.



        Add the following if statement around your ssh-add command:



        #!/bin/bash
        export SSH_ASKPASS=/usr/bin/ksshaskpass
        eval $(ssh-agent)

        if pstree -s -p $$ | grep Xsession; then
        exit
        fi

        /usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite


        Explanation: When you start a terminal the parent process is not a Xsession and therefore the ssh-add command is executed. At this time the kwallet is already unlocked and it does not ask for the passphrases of the ssh keys.






        share|improve this answer













        I have a workaround that I don't want to use anymore maybe it helps someone.



        Add the following if statement around your ssh-add command:



        #!/bin/bash
        export SSH_ASKPASS=/usr/bin/ksshaskpass
        eval $(ssh-agent)

        if pstree -s -p $$ | grep Xsession; then
        exit
        fi

        /usr/bin/ssh-add ~/.ssh/servers ~/.ssh/gitolite


        Explanation: When you start a terminal the parent process is not a Xsession and therefore the ssh-add command is executed. At this time the kwallet is already unlocked and it does not ask for the passphrases of the ssh keys.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 28 at 7:02









        iRaSiRaS

        200214




        200214






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f626423%2funlock-kwallet-at-login%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

            How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

            is 'sed' thread safe

            How to make a Squid Proxy server?