Is the cipherkey still a constant? (get rid of remember me stack traces in the log)

2025-04-06 Thread Steinar Bang
I'm trying to finally get rid of annoying log messages like this (error messages that have plagued me since I first started using shiro): https://gist.github.com/steinarb/7c06c116620be8460d7d9e58c9a6e6d6 I have googled and found this old thing (from mr. Shiro himself, Brian Demers): https://sta

Re: Is the cipherkey still a constant? (get rid of remember me stack traces in the log)

2025-04-06 Thread lenny
Hi, Sterinar, This is what I use to generate the key: openssl enc -aes-128-cbc -k secret -P -md sha256 Let me know if that works for you > On Apr 6, 2025, at 12:42 PM, Steinar Bang wrote: > > I'm trying to finally get rid of annoying log messages like this (error > messages that have plagued

Re: Is the cipherkey still a constant? (get rid of remember me stack traces in the log)

2025-04-06 Thread lenny
Yes, nothing changed there. > On Apr 6, 2025, at 2:19 PM, Steinar Bang wrote: > >> lenny-5o6p1tln9c5dpfhejli...@public.gmane.org: > >> Hi, Sterinar, >> This is what I use to generate the key: >> openssl enc -aes-128-cbc -k secret -P -md sha256 > >> Let me know if that works for you > > Th

Re: Is the cipherkey still a constant? (get rid of remember me stack traces in the log)

2025-04-06 Thread Steinar Bang
> lenny-5o6p1tln9c5dpfhejli...@public.gmane.org: > Hi, Sterinar, > This is what I use to generate the key: > openssl enc -aes-128-cbc -k secret -P -md sha256 > Let me know if that works for you Thanks, this means setting cipherkey to a constant is still the fix in 2.0.2? Ok, will try! And

Re: [VOTE] Release Apache Shiro 2.0.3

2025-04-06 Thread Benjamin Marwell
+1 Ben Am Sa., 5. Apr. 2025 um 23:38 Uhr schrieb : > > This is a call to vote in favor of releasing Apache Shiro version 2.0.3 > > Maven Staging repo: > https://repository.apache.org/content/repositories/orgapacheshiro-1063 > https://repository.apache.org/content/repositories/orgapacheshiro-1063/