News for hackers. Stuff that matters.
Re:Last.Backend – Visual Docker Containers Orchestration by lastbackend on Saturday April 18, 2015 @10:21AM (#9399528)
Yeah... sorry for that.. We will fix it on Monday also HTTPS. It's not good, but we tried to open product faster!
Re:Last.Backend – Visual Docker Containers Orchestration by subway on Saturday April 18, 2015 @10:53AM (#9399630)
Security should not be an afterthought. Especially not when you're trying to get me to trust my data to your platform.
Re:Last.Backend – Visual Docker Containers Orchestration by lastbackend on Saturday April 18, 2015 @11:01AM (#9399655)
You are right. But you can play with our platform this weekends, and on next week we'll opening agent to open-source and enable security. We have some delay with SSL delivery. :(
Re:Last.Backend – Visual Docker Containers Orchestration by tpg on Saturday April 18, 2015 @12:40PM (#9400034)
When I see security as a second-class citizen on user-visible elements, I assume that the same philosophy was applied on the parts I can't audit, even after the front-end stuff was fixed.
Re:Last.Backend – Visual Docker Containers Orchestration by runlevel1 on Saturday April 18, 2015 @04:58PM (#9401006)
Just get a free cert from StartSSL while you wait for your other cert to go through. It's better than nothing.

Asking people on HN to send their passwords in the clear is suicide.

Re:Last.Backend – Visual Docker Containers Orchestration by antocv on Saturday April 18, 2015 @12:11PM (#9399923)
I, for one, aint playin with anything you build. You aint coming close to having sudo on any of my machines if I can help it.

This shit with "enable security" as after-thought has to stop.

Re:Last.Backend – Visual Docker Containers Orchestration by meddlepal on Saturday April 18, 2015 @06:07PM (#9401266)
I agree. Basically makes me distrust the whole thing inside and out; who knows what other bs engineering practices were used in non visible parts of the stack? Shipping is great, but please don't ship insecure stuff as a product you want customers to use. Please.
Re:Last.Backend – Visual Docker Containers Orchestration by lastbackend on Saturday April 18, 2015 @06:24PM (#9401319)
We are enabled HTTPS. THX for your comments.

Next: installer update. Give us few minutes.

Re:Last.Backend – Visual Docker Containers Orchestration by meddlepal on Saturday April 18, 2015 @06:25PM (#9401324)
Great. Glad to see you're taking this seriously and hopefully it is a good lesson learned for the future!
Re:Last.Backend – Visual Docker Containers Orchestration by pauloschilling on Sunday April 19, 2015 @04:15PM (#9404684)
Here: https://www.ssllabs.com/ssltest/analyze.html?d=app.lastbacke...

Overall Rating: C This server is vulnerable to the POODLE attack. If possible, disable SSL 3 to mitigate. Grade capped to C.

Re:Last.Backend – Visual Docker Containers Orchestration by tlrobinson on Saturday April 18, 2015 @01:23PM (#9400191)
That attitude might work for a social network for cats, but it's not going to fly if you're asking users to trust you with their production servers.
Re:Last.Backend – Visual Docker Containers Orchestration by giovannibonetti on Saturday April 18, 2015 @01:41PM (#9400291)
You can get HTTPS for free (and hassle-free) if you use Cloudflare as your DNS server. Disclaimer: I am doing this publicity as a happy customer, without earning anything in return.
Re:Last.Backend – Visual Docker Containers Orchestration by tokenizerrr on Saturday April 18, 2015 @03:48PM (#9400760)
It's a bit more than DNS. It's sending all of your traffic through cloudflare, and they cache content/act as a CDN. But they can theoretically inspect/modify all traffic.
Re:Last.Backend – Visual Docker Containers Orchestration by lclarkmichalek on Saturday April 18, 2015 @10:24AM (#9399539)
Fair enough. Regardless, congrats on the release.