cornduck has quit [Remote host closed the connection]
aeris has quit [Remote host closed the connection]
Pipip has quit [Remote host closed the connection]
cornduck has joined #ruby
aeris has joined #ruby
Pipip has joined #ruby
Pipip has quit [Remote host closed the connection]
Pipip has joined #ruby
<terminalpusher>
ah, and streem is made by matz too
<terminalpusher>
but yeah Ruby does seem to be the most famous one
Pipip has quit [Changing host]
Pipip has joined #ruby
Pipip_ has joined #ruby
Pipip__ has joined #ruby
terminalpusher has quit [Remote host closed the connection]
Pipip has quit [Ping timeout: 260 seconds]
goldfish has joined #ruby
Pipip_ has quit [Ping timeout: 260 seconds]
Bounga has quit [Ping timeout: 268 seconds]
Pipip__ has quit [Ping timeout: 268 seconds]
dohtem has joined #ruby
Bounga has joined #ruby
Pipip has joined #ruby
gr33n7007h has quit [Read error: Connection reset by peer]
gr33n7007h has joined #ruby
Bounga has quit [Ping timeout: 252 seconds]
Bounga has joined #ruby
cornduck has quit [Remote host closed the connection]
cornduck has joined #ruby
_ht has joined #ruby
Nex6 has joined #ruby
taupiqueur_ has joined #ruby
taupiqueur has quit [Ping timeout: 260 seconds]
impermanence has joined #ruby
<impermanence>
regarding yesterday/today's 0-day it seems that logstash uses log4j
<impermanence>
has anyone here mitigated the 0-day for logstash and if so how did you do it?
<impermanence>
all the remediation articles talk about "setting the system property "log4j2.formatMsgNoLookups" to 'true'" but I'm not sure what is meant by "system property" here and how that would relate to logstash
<impermanence>
I can indeed see that there is a log4j.properties file within my logstash config, but no such property as the one listed above is present so I'm not sure if adding it and then bouncing logstash will work or if it would be set somewhere else related to logstash
taupiqueur_ has quit [Ping timeout: 268 seconds]
<adam12>
impermanence: Not sure of the fix yet, but if I see it come through I will let you know. Someone else is working on one on my team.
<impermanence>
adam12: we are mitigating it by setting the specified JVM param for log4j2 and then bouncing everything logstash related.
darkstardevx has quit [Read error: Connection reset by peer]
BSaboia has joined #ruby
taupiqueur has joined #ruby
BSaboia has quit [Quit: This computer has gone to sleep]
<nakilon>
instead of changing ' with ", back and forth every time you add or remove interpolation just use " always
<adam12>
hd1: Try closing stdin after you write it.
<adam12>
i.write(); i.close
<nakilon>
the only reason why people use ' is that one man with no experience several years ago declared that all rubyists should adobt his standard where he chose ' randomly or to consume less ink when he prints the code on paper, oidk
<adam12>
(I use double quotes everywhere. It's one less thing to think about)
<nakilon>
and that leads to bugs again and again
<nakilon>
or .flush
<weaksauce>
yeah you need to write or flush it before the program does its thing
<hd1>
doesn't help
<nakilon>
also there is a typo in "pasphrase" but that is irrelevant
<nakilon>
hd1 show us the current version
* nakilon
still bets on "
<adam12>
Likely '"passphrase"' could just be 'passphrase'
<adam12>
Since that's the whole point of arg splitting.
<adam12>
I'd be surprised if the close isn't necessary tho, since there's a signal needed to indicate that the program is done with input (ctrl-d and such)