The easiest way will be to change application.crypto.aes.transformation to something available everywhere (e.g. disabled PKCS5 padding), but still that's interesting how it gets encrypted. Sad I know nothing about Scala & Java so I cannot really debug it :(
On Thursday, February 27, 2014 2:59:43 PM UTC+2, Kay Röpke wrote: > > It looks like a signature from playframework to me. > I would need to debug a little to figure it out, we really didn't > anticipate creating these cookies outside of the play. > > I think it's better if we solve this problem the proper way, by supporting > remote_user. Generating the cookie seems very brittle to me :( > > On Wednesday, February 26, 2014 2:57:58 PM UTC+1, Егор Морозов wrote: >> >> Btw, also there's first part in the cookie: >> "*bbf13a266d32aef6f89fb35f250db77d15f04516-sessionid* >> =e6c12bace0608a422bf03954086e4d0a2ec64e7396a95871af55d986d3c7517968aadfc203975fdc8433e824533229dd" >> >> What is bbf13...? Looks like the length of session id without dashes is >> different. >> > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
