#taskwarrior

/

      • parsnip
        nearly had convulsions trying to navigate that taskserver troubleshooting doc
      • i don't see any certs that have expired
      • oh well, i guess nuke all the certs and redo it
      • :( kind of defeats the purpose of "follow the steps"
      • when handed a labrynth
      • *labyrinth
      • mrqubo has quit
      • argh, redid the certs, get Handshake failed. The certificate is NOT trusted. The certificate chain uses expired certificate.
      • seems i previously was using some letsencrypt certs or something, so maybe trying that out suddenly blows up in my face today.
      • great! works! what i was trying to say was, thank you for awesome software!
      • paininabox joined the channel
      • hfp
        I'm at my wits end. I have this error "Sync failed. Either your credentials are incorrect, or your account doesn't exist on the Taskserver." and I don't understand why.
      • it says the user in the ord doesn't exist, and yet I created it
      • any ideas?
      • eh, it turns out taskd and taskwarrior are _really_ anal regarding the CN, even if trust is set to allow all on both sides
      • and the error messages aren't very descriptive, I think that's what made it so hard
      • but I got it to work :) just have to clean it all up and I'll share the docker-compose if others need it
      • morethantwo joined the channel
      • morethantwo has quit
      • Nihl joined the channel
      • morethantwo joined the channel
      • morethantwo has quit
      • gour joined the channel
      • morethantwo joined the channel
      • morethantwo has quit
      • morethantwo joined the channel
      • Nihl has quit
      • morethantwo has quit
      • Nihl joined the channel
      • Nihl has quit
      • Nihl joined the channel
      • Nihl has quit
      • Nihl joined the channel
      • fmb00kworm joined the channel
      • fmb00kworm
        THIS IS AN EMERGENCY NOTICE THIS IS NOT SPAM: THIS NOTICE IS CURRENTLY GOING OUT TO ALL CHANNELS THROUGH THE FREENODE EMERGENCY NOTIFICATION SYSTEM: GRUMBLE HAS INADVERTENTLY NOT RESET THE FREENODE SECURITY PASSWORD CAUSING A BREAK IN FREENODE SECURITY WHERE ALL PASSWORDS HAVE BEEN RELEASED. PLEASE SEE GRUMLE IN #FREENODE FOR INFORMATION ON HOW TO SECURE YOUR ACCOUNT!!
      • THIS IS AN EMERGENCY NOTICE THIS IS NOT SPAM: THIS NOTICE IS CURRENTLY GOING OUT TO ALL CHANNELS THROUGH THE FREENODE EMERGENCY NOTIFICATION SYSTEM: GRUMBLE HAS INADVERTENTLY NOT RESET THE FREENODE SECURITY PASSWORD CAUSING A BREAK IN FREENODE SECURITY WHERE ALL PASSWORDS HAVE BEEN RELEASED. PLEASE SEE GRUMLE IN #FREENODE FOR INFORMATION ON HOW TO SECURE YOUR ACCOUNT!!
      • THIS IS AN EMERGENCY NOTICE THIS IS NOT SPAM: THIS NOTICE IS CURRENTLY GOING OUT TO ALL CHANNELS THROUGH THE FREENODE EMERGENCY NOTIFICATION SYSTEM: GRUMBLE HAS INADVERTENTLY NOT RESET THE FREENODE SECURITY PASSWORD CAUSING A BREAK IN FREENODE SECURITY WHERE ALL PASSWORDS HAVE BEEN RELEASED. PLEASE SEE GRUMLE IN #FREENODE FOR INFORMATION ON HOW TO SECURE YOUR ACCOUNT!!
      • Nihl gour paininabox palo ksalman Pest ntnn xorkle jrabbit notizblock viq rjc swimmer nutron dbe danmichaelo bqf DoomPatrol languitar scorphus hfp ducer eelvex task-git yushyin parsnip TheBaronHimself ifbizo welterde AlexanderS jelle pbeckingham coddingtonbear ddeimeke lydgate bleader dkrm xcm spredzy ayyjayess[m] romangeeko tbabej doulos05 ackthet jcgruenhage Haudegen[m] bbigras-- bstinson ggVGc mitfree[m] pleia2 callahad zopsi irl Drajwer supercow
      • fmb00kworm has quit
      • Minoru
        "emergency notification system" is called "server notice", not some unregistered nickname going around channels posting stuff. There weren't any server notices since yesterday when services (ChanServ, Nickserv etc.) were restarted
      • (posting this for the sake of people who's new-ish to IRC)
      • Haudegen joined the channel
      • spredzy has quit
      • Nihl has quit
      • Nihl joined the channel
      • viq joined the channel
      • Nihl has quit
      • Nihl joined the channel
      • Nihl has quit
      • Nihl joined the channel
      • Nihl has quit
      • task-git
        *** libshared - commit 9e5c930 in "HEAD", Laurence: Fix Path::expand, close #7.
      • paininabox has quit
      • *** libshared - commit 230c63b in "HEAD", Paul Beckingham: LI #7: Path::expand() doesn't correctly expand some paths
      • hfp
        is there an api for taskd? what are the client.{cert,key}.pem for then?
      • pbeckingham
        hfp: Yes, you can extract runtime statistics using api. Note that I have renamed client.{key,cert} to api.{key,cert} recently.
      • task-git
        *** Taskwarrior - commit edfa8ed in "2.5.2", Paul Beckingham: Cleanup: Removed file that was accidentally cherry-picked
      • *** Taskwarrior - commit 376d336 in "2.5.2", Paul Beckingham: libshared: Upgraded to 230c63bd385b2a5a6ee5eb431df54b0c5c229b4d
      • hfp
        pbeckingham: thanks, is there a doc somewhere for what the api can do and how?
      • pbeckingham
      • hfp
        thanks. no way to add users via the api, right?
      • pbeckingham
        No. There was once, but I killed that a long time ago when there was an effort to do security properly.
      • hfp
        alright. one more: why is it that if I start taskd with 0.0.0.0 as the server names, it won't allow users (the CN is the hostname)? how does that work: https://github.com/jrabbit/taskd-docker/blob/ma... ?
      • sm has quit
      • pbeckingham
        No idea. The point of the certs is to establish identity, so that's why everything has to match.
      • sm joined the channel
      • hfp
        out of curiosity, why not leverage ssh for example for server and client sync?
      • mrqubo joined the channel
      • and just to clarify, the CN has to match `hostname -f` where taskd is running, but it doesn't need to match the FQDN the taskd machine has, right? I could set the hostname and CN to `mytaskserver` and use taskd.example.com to contact it, it would work?
      • pbeckingham
        Why not leverage ssh? You mean let the client run processes on the server? That isn't better.
      • The certs are there to eliminate man0in-the-middle attacks, and what you're describing sounds like trying to get around that.
      • mrqubo_ joined the channel
      • mrqubo has quit
      • mrqubo_ is now known as mrqubo
      • hfp
        pbeckingham: I'm looking for a solution how to have taskd run in a docker-compose service without breaking the certificate setup. Docker gives containers random hostnames, and if I want to pin the hostname then it's not portable for others to use it. I thought of putting a nginx reverse stream proxy but I don't think that will work since it would have to mitm the connection to make it look like the
      • docker container's hostname is also the FQDN.
      • jcrben
        ksalman: the context will be moved out of the taskrc eventually https://github.com/GothenburgBitFactory/taskwar... - my taskrc has only 1 line: include ~/dotfiles/config/task/task.versioned
      • pbeckingham
        jcrben: So disciplined!
      • jcrben
        pbeckingham: anal retentive. if I was disciplined I'd go to the gym more regularly :)
      • mrqubo has quit
      • mrqubo joined the channel
      • Drajwer
        hfp IMO http protocol would be better for sync
      • you could just use basic auth and SSL cert
      • and youre good to go
      • actually it could work in a similiar way to git - ship a „taskwarrior sync” app and communicate with this app over any protocol because why not?
      • gour_ joined the channel
      • gour has quit
      • cepxuo
        Is it possible to make a recurrent task that must be done the last day of the month?
      • ksalman
        jcrben: oh i see, thanks!
      • gour_ is now known as gour
      • pbeckingham
        cepxuo: No, only on fixed dates. So if you said "due:28th recur:monthly" that's the closest it gets.
      • woshty joined the channel
      • mrqubo has quit
      • gour
        cepxuo: that's 2.6.0 feature ;)
      • Guest96535 joined the channel
      • Voldenet21GEYE joined the channel
      • Voldenet21GEYE
        Global Notice] Hello freenode, you may have noticed 2 days ago many users got logged out of their NickServ accounts. After our investigation, we have come to the conclusion one or more of our sponsored servers have been compromised. Please change your password IMMEDIATELY. More details are available in #freenode with the command !help
      • Global Notice] Hello freenode, you may have noticed 2 days ago many users got logged out of their NickServ accounts. After our investigation, we have come to the conclusion one or more of our sponsored servers have been compromised. Please change your password IMMEDIATELY. More details are available in #freenode with the command !help
      • Global Notice] Hello freenode, you may have noticed 2 days ago many users got logged out of their NickServ accounts. After our investigation, we have come to the conclusion one or more of our sponsored servers have been compromised. Please change your password IMMEDIATELY. More details are available in #freenode with the command !help
      • Haudegen woshty gour sm viq palo ksalman Pest ntnn xorkle jrabbit notizblock rjc swimmer nutron dbe danmichaelo bqf DoomPatrol languitar scorphus hfp ducer eelvex task-git yushyin parsnip TheBaronHimself ifbizo welterde AlexanderS jelle pbeckingham coddingtonbear ddeimeke lydgate bleader dkrm xcm ayyjayess[m] romangeeko tbabej doulos05 ackthet jcgruenhage Haudegen[m] bbigras-- bstinson ggVGc mitfree[m] pleia2 drozdziak1 yo61 Netmage Guest50286 G
      • Voldenet21GEYE has quit
      • ackthet
        but why
      • ggVGc
        what is going on
      • is freenode under some kind of siege
      • Minoru
        admins just sent a notice through IRC, have you seen it, ggVGc?
      • ggVGc
        no
      • ah, wait
      • now I have
      • Minoru
        ;)
      • gour has quit
      • palo_ joined the channel
      • palo_ joined the channel
      • palo has quit
      • paininabox joined the channel
      • paininabox has quit
      • rjc has quit
      • dbe has quit