Raf

I am not sure how to preserve backwards compatibility in this case. There is not enough information in the beacon registration message to differentiate an "old" beacon from a "new"...

Yeah - this is only affecting the display of the beacon time, not the actual beacon itself.

Hey @pooki3bear - execute and shell seem to work fine as of Sliver 1.5.10 (see below). Could you give it a try and report back? 

@05t3 I think you have the Kali packaged version of Sliver installed as well as the official release. I suggest running `apt remove sliver` and sticking with the official releases...

I wrote a fix that should _hopefully_ address this issue by limiting concurrent fetches from the armory for indexes and package signatures to 10 requests at a time. I picked...

@rkervella I think I identified the issue and submitted a [PR upstream](https://github.com/reeflective/readline/pull/61). I tested my fix with Sliver, and it seems to restore the behavior back to what we have...

It looks like this issue has been fixed since the current release version was built. Using a client binary built from the current `master` branch, installing aliases from the armory...

@R0ttCyph3r - Thanks for bringing this to our attention. It should be fixed by #1686. Once the fix is live, please test and let us know if the issue still...

@gh0-0st - I cannot replicate what you are seeing with the latest build (53c61cb0241f30492bf719979b10647c9d48c7b4):  Also, I am surprised that `armory install` gives the output you showed. It should display...