Thanks so much for this initiative, I'll make sure to spread the knowledge
you decided to share with us. =)
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
Sounds good Joe
On Sun, Mar 17, 2019 at 9:00 AM Joe Guerra wrote:
> oh, I fixed it. I had done a merge, and my gemlock file had some weird
> stuff in it.
>
> I just deleted the file, did a bundle install, pushed it back to
> github and was able to build it.
>
> On Saturday, March 16, 2019 at
oh, I fixed it. I had done a merge, and my gemlock file had some weird
stuff in it.
I just deleted the file, did a bundle install, pushed it back to github and
was able to build it.
On Saturday, March 16, 2019 at 3:10:40 PM UTC-4, David Merrick wrote:
>
> Between switching gems and a
Between switching gems and a possible error or missing file in initialize
has created a problem is my guess.
Cheers Dave
On Sun, Mar 17, 2019 at 4:32 AM Joe Guerra wrote:
> oh, it must be something to do with ruby-sass that I updated because of
> some vulnerabilities.
>
> On Saturday, March
They are only valid for 15 minutes and then they are never going to work again.
They don't matter. I suppose if you had enough of them you could brute-force
out what the secret key was, but that's a nation-state level of effort. Are
your users (or their haters) in that league?
Walter
> On Mar
oh, it must be something to do with ruby-sass that I updated because of
some vulnerabilities.
On Saturday, March 16, 2019 at 11:30:26 AM UTC-4, Joe Guerra wrote:
>
> I can't figure out why I got a build fail on heroku... I just switched a few
> items in my gem file, pushed it to git, and tried
It varies on each request
https://medium.com/rubyinside/a-deep-dive-into-csrf-protection-in-rails-19fa0a42c0ef
On Sat, Mar 16, 2019 at 2:19 AM 0x01 wrote:
> I do use Heroku and pipe logs to Papertrail (log aggregation service).
> Also, logs are stored in Amazon S3 for some time.
>
> If these
I do use Heroku and pipe logs to Papertrail (log aggregation service).
Also, logs are stored in Amazon S3 for some time.
If these logs get compromised, can these tokens be used again (i.e. are
these tokens reusable?)
Thanks.
пятница, 15 марта 2019 г., 23:08:48 UTC+4 пользователь Joe Guerra
8 matches
Mail list logo
