podman

Activity Graph

Page 1 of 4 | Next »

2019-06-17

[18:24:40] podman: Ping timeout: 264 seconds
[18:26:21] podman: has joined #ruby
[18:26:21] podman: has joined #RubyOnRails

2019-05-24

[08:06:26] podman: Ping timeout: 252 seconds
[08:08:50] podman: has joined #ruby
[08:08:50] podman: has joined #RubyOnRails

2019-05-20

[06:47:24] podman: Read error: Connection reset by peer
[06:47:36] podman: has joined #ruby
[06:47:36] podman: has joined #RubyOnRails

2019-04-13

[16:49:50] podman: *.net *.split

2019-03-29

[00:10:11] podman: has joined #RubyOnRails
[00:11:25] podman: Hi all. I'm running into some problems connecting to a standalone selenium server in docker using selenium/standalone-chrome with capybara and rspec. anyone have any experience getting this type of setup working?
[00:13:41] podman: has joined #ruby

2019-03-20

[18:30:26] podman: Ping timeout: 252 seconds

2019-03-11

[22:14:05] podman: has joined #RubyOnRails

2018-09-03

[19:10:25] podman: *.net *.split

2018-07-20

[00:07:24] podman: *.net *.split
[00:15:28] podman: has joined #RubyOnRails
[00:15:46] podman: has joined #ruby

2018-06-20

[03:50:31] podman: Ping timeout: 276 seconds
[05:21:37] podman: has joined #RubyOnRails
[05:21:44] podman: has joined #ruby
[05:57:07] podman: Ping timeout: 256 seconds
[06:25:13] podman: has joined #RubyOnRails
[06:25:19] podman: has joined #ruby

2018-06-01

[03:44:47] podman: *.net *.split
[07:47:36] podman: has joined #ruby
[07:47:37] podman: has joined #RubyOnRails

2018-05-29

[02:47:15] podman: *.net *.split
[02:47:46] podman: has joined #RubyOnRails
[02:48:02] podman: has joined #ruby

2018-05-19

[15:33:50] podman: Remote host closed the connection
[15:36:11] podman: has joined #RubyOnRails
[15:36:17] podman: has joined #ruby

2018-05-06

[10:28:01] podman: has joined #RubyOnRails
[10:28:07] podman: has joined #ruby

2018-04-25

[12:25:46] podman: *.net *.split
[12:27:20] podman: has joined #ruby
[12:27:34] podman: has joined #RubyOnRails
[15:01:16] podman: *.net *.split
[15:03:04] podman: has joined #RubyOnRails
[15:03:17] podman: has joined #ruby

2018-04-10

[14:02:10] podman: has joined #RubyOnRails
[14:02:16] podman: has joined #ruby

2018-03-10

[18:16:43] podman: Ping timeout: 256 seconds
[18:17:03] podman: has joined #RubyOnRails
[18:17:09] podman: has joined #ruby

2018-03-02

[04:11:07] podman: Read error: Network is unreachable
[04:15:26] podman: has joined #RubyOnRails
[04:15:33] podman: has joined #ruby

2018-02-28

[23:23:47] podman: Read error: Connection reset by peer
[23:24:03] podman: has joined #RubyOnRails
[23:24:11] podman: has joined #ruby
[23:25:04] podman: Max SendQ exceeded
[23:25:27] podman: has joined #RubyOnRails
[23:25:34] podman: has joined #ruby

2017-12-27

[19:14:46] podman: Ping timeout: 264 seconds
[21:32:12] podman: has joined #RubyOnRails
[21:32:18] podman: has joined #ruby

2017-12-12

[17:28:03] podman: I'm running into an issue w/ rails 3 where i have config.force_ssl set to true, but have a namespace that doesn't use SSL. The issue i'm having is that sessions/cookies aren't being set for that namespace. any idea how to allow it to create them?
[17:59:33] podman: fryguy: where, specifically?
[18:00:09] podman: sorry, forgot a bit of information. SSL should only be disabled within that namespace for certain hostnames
[18:00:20] podman: yes, i need it everywhere except a specific namespace
[18:01:04] podman: right, so i'm trying to see if there is a way to make them not secure in certain instances
[18:01:21] podman: like if a hostname matches a specific pattern
[18:01:31] podman: yes, but i can create non-secure cookies
[18:01:44] podman: https://apidock.com/rails/v3.2.13/ActionDispatch/Request/session_options%3D
[18:02:20] podman: ah, so i can't use a proc? https://github.com/rails/rails/blob/2d04bdd86fb4a9c69e1ca1ffe92188a9ca4f88c8/railties/lib/rails/application/default_middleware_stack.rb#L49
[18:02:31] podman: it looks like it just sets it to true if it's ever true, right?
[18:02:47] podman: so, is there a work around to something like this?
[18:03:40] podman: i guess i could override all cookies to not be secure?
[18:04:21] podman: until i have a better, long term, solution
[18:05:22] podman: or just manually take over session management?
[18:05:41] podman: is it possible to use a different session store for a namespace?
[18:14:55] podman: fryguy: i'm guessing the answers are all no?

2017-09-04

[18:38:25] podman: *.net *.split
[20:27:28] podman: has joined #RubyOnRails
[20:27:34] podman: has joined #ruby

2017-08-14

[23:51:23] podman: *.net *.split
[23:56:32] podman: has joined #RubyOnRails
[23:56:34] podman: has joined #ruby

2017-07-12

[12:41:23] podman: Ping timeout: 246 seconds
[14:37:19] podman: has joined #RubyOnRails
[14:37:25] podman: has joined #ruby

2017-06-20

[00:17:21] podman: *.net *.split
[00:22:42] podman: has joined #RubyOnRails

2017-05-09

[00:03:29] podman: Ping timeout: 240 seconds
[00:03:40] podman: has joined #RubyOnRails
[00:03:46] podman: has joined #ruby

2017-05-04

[00:20:44] podman: has joined #RubyOnRails
[00:20:50] podman: has joined #ruby
[03:11:47] podman: *.net *.split
[05:13:01] podman: has joined #RubyOnRails
[05:13:07] podman: has joined #ruby

2017-05-03

[22:28:41] podman: Ping timeout: 240 seconds

2017-05-01

[16:41:11] podman: *.net *.split
[18:07:25] podman: has joined #RubyOnRails
[18:07:31] podman: has joined #ruby

2017-04-30

[12:29:04] podman: Remote host closed the connection
[12:37:25] podman: has joined #RubyOnRails
[12:37:31] podman: has joined #ruby

2017-04-13

[14:51:59] podman: has joined #RubyOnRails
[14:52:05] podman: has joined #ruby

2016-07-18

[17:05:45] podman: Ping timeout: 272 seconds
[17:10:19] podman: has joined #RubyOnRails
[17:10:25] podman: has joined #ruby

2016-06-15

[15:16:21] podman: Hi there! I'm wondering how useful / needed ip spoofing checking really is. We're seeing a few users run into this and the only solution for them would be to disable the check. Is ip spoofing something I should be worried about?
[15:26:15] podman: epochwolf: internet -> AWS ELB -> nginx -> unicorn with proxy_pass
[15:28:29] podman: epochwolf: i have `poxy_set_header X-Forwarded-For $proxy_add_x_forwaded_for;`
[15:29:16] podman: epochwolf: this is a pretty rare occurrence. but we do have a potentially big client that can't access our site because their proxy must be configured incorrectly
[15:33:32] podman: epochwolf: yeah, i saw that. it didn't seem to give conclusive guidance either way
[15:34:28] podman: unless that's just saying we can trust our proxy (ELB in this case)
[15:35:09] podman: workmad3: to the best of my knowledge, no?
[15:38:59] podman: i guess the real question is, do i need to worry about IP Spoofing?
[15:39:43] podman: well the throttling is taking place in nginx
[15:39:55] podman: not rails (although that might change)
[15:40:51] podman: workmad3: $binary_remote_addr
[15:41:25] podman: workmad3: no, it's the remote client IP (at least it is in practice)
[15:41:34] podman: not sure what ELB is doing with headers
[15:41:49] podman: http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/x-forwarded-headers.html
[15:42:32] podman: real_ip_header X-Forwarded-For;
[15:42:43] podman: i have that in my http block
[15:43:38] podman: yeah, set_real_ip_from is set
[15:44:14] podman: workmad3: dunno
[15:44:32] podman: so, basically ignore the proxy chain?
[15:45:00] podman: workmad3: in that case, is it any different than turning off ip_spoof_check in rails?
[15:45:49] podman: actually, in this case i think the spoof check would still fail
[15:47:54] podman: so client-ip is set to something like 172.x.x.x and x-forwarded-for is set to '172.x.x.x, 217.x.x.x, 217.x.x.x1'.
[15:48:13] podman: but it should be the right most address it's checking against, correct?
[15:48:25] podman: is their proxy just a piece of crap?
[15:49:42] podman: workmad3: right. and that is what rails is checking for a spoofing attack
[15:50:25] podman: yeah, in this case it's a websense proxy
[15:52:07] podman: epochwolf: haven't even gotten to deal with their IT department yet
[15:52:19] podman: just trying to see if we can make this easy for them
[15:52:54] podman: workmad3: so, change: proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; to proxy_set_header X-Forwarded-For $remote_addr; is what you're saing?
[15:53:43] podman: workmad3: of course
[15:56:47] podman: ok, i actually see what's happening here
[15:56:56] podman: it's pretty weird
[15:57:23] podman: so, the IP address that's being sent is a "trusted" proxy
[15:58:40] podman: i think the solution here would be to just drop the client-ip header
[16:00:23] podman: workmad3: epochwolf: what do you guys think? that shouldn't cause any major issues, right?
[16:07:22] podman: great, now i just have to figure out how to do that
[16:08:32] podman: epochwolf: cool, yeah, looking into it
[16:09:08] podman: epochwolf: http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_hide_header
[16:09:13] podman: epochwolf: looks like that's what i want
[16:11:06] podman: epochwolf: oh, interesting
[16:12:28] podman: epochwolf: yep, you're correct :) http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_set_header
[16:30:02] podman: epochwolf: workmad3: alright, have that running in production. seems like people's correct IP address is still being set and no more ipspoofing false positives
[16:31:06] podman: epochwolf: sometimes i hate the internet
[16:31:41] podman: sounds about right
[16:38:14] podman: cschneid: use CSS instead?
[16:38:44] podman: cschneid: yep

2016-06-10

[00:19:04] podman: Ping timeout: 264 seconds
[00:20:56] podman: has joined #RubyOnRails
[00:21:00] podman: has joined #ruby

2016-06-09

[05:25:41] podman: Ping timeout: 260 seconds
[05:31:19] podman: has joined #RubyOnRails
[05:31:23] podman: has joined #ruby

2016-05-18

[08:45:39] podman: Ping timeout: 250 seconds

2016-05-06

[07:58:19] podman: Ping timeout: 244 seconds
[08:00:06] podman: has joined #RubyOnRails
[08:00:10] podman: has joined #ruby

2016-04-17

[07:56:53] podman: *.net *.split
[07:59:13] podman: has joined #RubyOnRails
[07:59:14] podman: has joined #ruby

2016-04-15

[15:12:04] podman: Ping timeout: 260 seconds
[15:24:04] podman: has joined #ruby
[15:24:04] podman: has joined #RubyOnRails
[17:27:55] podman: *.net *.split
[17:49:31] podman: has joined #ruby
[17:49:31] podman: has joined #RubyOnRails

2016-04-13

[18:41:51] podman: Remote host closed the connection
[18:44:22] podman: has joined #ruby
[18:44:22] podman: has joined #RubyOnRails

2016-04-11

[16:55:01] podman: If I'm upgrading from a 3.2 app, should I bother upgrading to 4 or should I just skip to 5 even though it's still in beta?
[16:58:36] podman: arup_r: thanks. will check it out
[17:00:04] podman: mwlang: the last time I upgraded this app was from 2 to 3 and 4 came out a few months later so... i just didn't bother. I don't want the same thing to happen again
[17:00:50] podman: mwlang: one can hope!

2016-03-31

[03:33:27] podman: Ping timeout: 246 seconds
[03:38:48] podman: has joined #RubyOnRails
[03:38:52] podman: has joined #ruby

2016-03-24

[21:34:26] podman: Ping timeout: 240 seconds
[21:34:49] podman: has joined #RubyOnRails
[21:34:53] podman: has joined #ruby

2016-03-18

[19:19:26] podman: has joined #RubyOnRails

2016-03-17

[02:19:41] podman: *.net *.split
[02:25:20] podman: has joined #ruby

2016-03-10

[00:49:08] podman: Ping timeout: 248 seconds

2016-03-02

[01:20:16] podman: has joined #ruby
[01:20:16] podman: has joined #RubyOnRails
[01:20:16] podman: has joined #ruby-community
[05:54:11] podman: Quit: Connection closed for inactivity
[15:26:59] podman: has joined #RubyOnRails
[15:26:59] podman: has joined #ruby-community
[15:27:03] podman: has joined #ruby

2016-03-01

[01:34:11] podman: Quit: Connection closed for inactivity
[16:00:47] podman: has joined #ruby
[16:00:47] podman: has joined #RubyOnRails
[16:00:47] podman: has joined #ruby-community
[18:14:11] podman: Quit: Connection closed for inactivity
[18:37:04] podman: has joined #ruby
[18:37:04] podman: has joined #RubyOnRails
[18:37:04] podman: has joined #ruby-community
[23:44:11] podman: Quit: Connection closed for inactivity

2016-02-29

[02:24:10] podman: Quit: Connection closed for inactivity
[15:28:08] podman: has joined #ruby
[15:28:08] podman: has joined #RubyOnRails

2016-02-28

[23:02:13] podman: has joined #ruby
[23:02:13] podman: has joined #RubyOnRails

2016-02-24

[16:54:09] podman: Quit: Connection closed for inactivity

2016-02-22

[11:40:50] podman: Ping timeout: 240 seconds
[11:42:45] podman: has joined #ruby
[11:42:45] podman: has joined #RubyOnRails
[17:34:08] podman: Quit: Connection closed for inactivity
[18:01:36] podman: has joined #ruby
[18:01:36] podman: has joined #RubyOnRails

2016-02-18

[22:20:49] podman: has joined #ruby
[22:20:49] podman: has joined #RubyOnRails

2016-02-17

[01:44:07] podman: Quit: Connection closed for inactivity
[20:14:07] podman: Quit: Connection closed for inactivity

2016-02-16

[05:54:07] podman: Quit: Connection closed for inactivity
[19:40:52] podman: has joined #ruby
[19:40:52] podman: has joined #RubyOnRails

2016-02-15

[19:38:03] podman: has joined #ruby
[19:38:03] podman: has joined #RubyOnRails

2016-02-13

[01:24:06] podman: Quit: Connection closed for inactivity

2016-02-12

[00:04:06] podman: Quit: Connection closed for inactivity
[19:28:00] podman: has joined #ruby
[19:28:00] podman: has joined #RubyOnRails

2016-02-09

[15:59:37] podman: has joined #ruby
[15:59:37] podman: has joined #RubyOnRails
[21:54:05] podman: Quit: Connection closed for inactivity

2016-02-06

[01:44:05] podman: Quit: Connection closed for inactivity

2016-02-05

[18:05:35] podman: has joined #ruby
[18:05:35] podman: has joined #RubyOnRails

2016-02-04

[00:44:04] podman: Quit: Connection closed for inactivity
[19:10:32] podman: has joined #ruby
[19:10:32] podman: has joined #RubyOnRails
[23:14:04] podman: Quit: Connection closed for inactivity

2016-02-01

[20:14:52] podman: has joined #ruby
[20:14:52] podman: has joined #RubyOnRails

2016-01-29

[01:44:02] podman: Quit: Connection closed for inactivity

2016-01-28

[21:21:04] podman: has joined #ruby
[21:21:04] podman: has joined #RubyOnRails

2016-01-26

[04:04:01] podman: Quit: Connection closed for inactivity