552 karma · joined August 4, 2014
--
about me & contact: https://dadario.com.br
best pic ever: https://jayub-intercomm.weebly.com/uploads/6/0/2/8/60283505/1443822731.png
--
I kinda like to code. I more or less like to do product management. But I'm always delighted to ship products that people love.
--
"If you want to set off and go develop some grand new thing, you don't need millions of dollars of capitalization. You need enough pizza and Diet Coke to stick in your refrigerator, a cheap PC to work on and the dedication to go through with it." - John Carmack (quote stolen from HN user nchelluri)
--
"when the rubber meets the road", love this quote
--
"(...) you want to do projects that are inspiring and that make people excited about the future. my life's got to be about more than just solving problems who want to get up in the morning and say yes I'm looking forward to that thing happening (...)" mr musk
-- loginwithhn
wX4oPqNdLt
Leonardo da Vinci seems to be one of those who procrastinated/thought a lot.
That's precisely what I wanted to know more, because I already use The Great Suspender. You know, I usually blow my chrome with 50+ tabs, thus extensions like these really save memory for me, although a tab is still a process from what I understand and even in 'hibernated' mode it still consumes some memory. Yours reduces it even more? If yes, by how much? Thank you
"Owasp Testing Guide V4" is a must read for web hackers, at least for starters: https://www.owasp.org/index.php/OWASP_Testing_Guide_v4_Table...
OWASP has vulnerable application projects for you to play with, such as WebGoat "https://www.owasp.org/index.php/Category:OWASP_WebGoat_Proje..., but there are many applications like these such as "DVWA - Damn Vulnerable Web Application" and variants in Node JS (https://n0where.net/damn-vulnerable-node-application-dvna/)
I also developed two free courses on "WordPress Security" and "Docker Security" https://dadario.com.br/courses/
The point is to learn development / infrastructure first, then study attacks and defense to develop a security mindset. Get involved in bug bounties, but learn how to fix, don't let your code skills rust. Then learn more security concepts, how to build a corporate security program and keep moving :)
There's also a very famous book in the area: "The Web Application Hacker's Handbook" http://mdsec.net/wahh/
"Two months after damaging data breach, Target stock has its best day in 5 years" http://blogs.marketwatch.com/behindthestorefront/2014/02/26/...
"Sad reality: It's cheaper to get hacked than build strong IT defenses" http://www.theregister.co.uk/2016/09/23/if_your_company_has_...
"The Cost of Cyberattacks Is Less than You Might Think" https://www.schneier.com/blog/archives/2016/09/the_cost_of_c...
And my take on this topic
"Is it really cheaper to get hacked?" https://dadario.com.br/is-it-really-cheaper-to-get-hacked/
Indeed, but I was referring to a word that contains the meaning of "self-made" when it should be something like "together-made". The other words as you said is fine. Thanks for replying.
> This flexibility comes at the cost of some bulk: The `microsoft/windowsservercore` image takes up 10GB.
Hope next versions shrink the image size.
> And the Nano Server base image is an order of magnitude smaller than Windows Server Core, meaning it has less dependencies and surface area to keep updated.
I wonder how smaller it is. Do you have any estimate here?
```ruby
namespace :app do
desc "Generate static pages"
task static: :environment do
pages = {
'/' => 'index.html'
}
app = ActionDispatch::Integration::Session.new(Rails.application)
pages.each do |route, output|
puts "Generating #{output}..."
outpath = File.join ([Rails.root, 'public', output])
resp = app.get(route)
if resp == 200
File.delete(outpath) if File.exists?(outpath)
if app.response.body.empty?
puts "[ no content ]"
else
encoded_body = app.response.body.encode(
'UTF-8',
{:invalid => :replace, :undef => :replace, :replace => '?'}
)
File.open(outpath, 'w') do |f|
f.write(encoded_body)
end
end
else
puts "Error generating #{output}!"
end
end
end
end```
Well, it's not recommended:
>> Due to the risk that SMS messages may be intercepted or redirected, implementers of new systems SHOULD carefully consider alternative authenticators. If the out of band verification is to be made using a SMS message on a public mobile telephone network, the verifier SHALL verify that the pre-registered telephone number being used is actually associated with a mobile network and not with a VoIP (or other software-based) service. It then sends the SMS message to the pre-registered telephone number. Changing the pre-registered telephone number SHALL NOT be possible without two-factor authentication at the time of the change. OOB using SMS is deprecated, and may no longer be allowed in future releases of this guidance.
Source: NIST (https://pages.nist.gov/800-63-3/sp800-63b.html)
> Shameful? Sure, if you know about the vulnerabilities. Maybe from a non-secure mindset you're right, but my point is about strategies for a security program. And it also has another problem, without prior checks you'll end up paying much more money. Facebook and Google paid millions already, but that amount would be much higher if they didn't check for vulnerabilities in their home.
Talking about security strategies, you don't really need to know about the vulnerabilities in order to consider this very act "shameful". It's just that you're lacking due diligence. You shouldn't blindly trust bug hunters as a single mechanism to reduce the number of bugs.