On 7 aug. 2014, at 05:01, David wrote:
> Is there any downside to adding @STRENGTH to the cipher list? From "man
> ciphers" (openssl), "the cipher string @STRENGTH can be used at any point to
> sort the current cipher list in order of encryption algorithm key length."
>
> For example, the cu
> On 14 aug. 2015, at 00:16, b...@cogs.com wrote:
>
> I working through installing Prosody and I really like it so far. I have a
> set-up that seems to be installed but when I try launch prosody I receive the
> message that I have lua 5.2 installed and lua 5.1 is required.
> My question is can
> On 19 okt. 2015, at 08:26, Pa He wrote:
>
> I'm having problems implementing the internal_hashed procedures in ruby. My
> setup is the following:
>
> I have a public-facing prosody 9.3 which does not allow inband registration.
> I'm writing a Ruby on Rails App
> which should insert the new
On 19 okt. 2015, at 13:40, Thijs Alkemade wrote:
>
>>
>> On 19 okt. 2015, at 08:26, Pa He wrote:
>>
>> I'm having problems implementing the internal_hashed procedures in ruby. My
>> setup is the following:
>>
>> I have a public-facing pr
> On 22 okt. 2015, at 18:21, Pa He wrote:
>
> Hi Thijs
>
> Thanks for your response. I see this wiki page seems to be the source of
> http://stackoverflow.com/questions/29298346/xmpp-sasl-scram-sha1-authentication/29299946#29299946
>
> Here is my console output:
>
> [1] pry(main)> clearpass
> On 23 okt. 2015, at 13:59, Pa He wrote:
>
> Hi Thijs
>
> Yes, this indeed helps: i got it working:
>
> key = OpenSSL::PKCS5.pbkdf2_hmac_sha1(pass, salt, iter, 20).unpack('H*')[0]
> => "a71aacc618c164ccf3efd2ae23b0061919844909"
>
> Gives me the correct saltedpass.
>
> Got some help from an
Hi Pawel,
You did not mention this, but from the log I’m concluding that the s are
routed through a MUC. Could it be that there are multiple instances of the
same bare JID behind one nick in the MUC? I think there can some unexpected
results when routing s in Prosody when that happens (like a resu
Hi Ying,
I don't know how Jappix works, but one approach to live help systems is to
create a new MUC (with a randomly generated name [1]) when a user requests the
help and then send invitations to the people who can offer help. Once one
person has accepted the invitation the user is informed that
