Titanous

20 ms·

151.
by Titanous 12y ago
Previously: https://news.ycombinator.com/item?id=7863856
152.
by Titanous 12y ago
>> Is there a draft specification available for libtrust? > https://github.com/docker/docker/issues/8093 https://github.com/docker/docker/issues/9015 libtrust does not
153.
by Titanous 12y ago
> There is nothing particularly new in Jonathan's post and I thank him for facilitating a conversation. Maybe not new to you or Docker Inc staff, but I don't see any warnings that a pull could result in complete compromise. On
154.
by Titanous 12y ago
Author here. > I wish the author had not omitted this crucial paragraph in the announcement he quotes: I did not quote this announcement, only linked to it. If this is intended to be prototype code, it should not be enabled by default, a
155.
Docker Image Insecurity(titanous.com)
263 points by Titanous 12y ago|100 comments
156.
by Titanous 12y ago
Here's the original: https://web.archive.org/web/20141201195306/https://blog.dock...
157.
by Titanous 12y ago
These may be the blog posts that you are thinking of: http://opine.me/a-better-way-to-store-password-hashes/ http://opine.me/all-your-hashes-arent-belong-to-us/ http://ethanheilman.tumb
158.
by Titanous 12y ago
We're working creating database appliances (think RDS/Elasticache/Heroku Postgres) at Flynn[0] (I'm one of the creators). [0] https://flynn.io
159.
by Titanous 12y ago
Flynn co-creator here. Short answer: A lot. At Flynn we're building solutions to what we see as the big problems that developers will face in the next few years. Deis seems to be solely focused on Heroku-like featureset. Flynn runs any
160.
by Titanous 12y ago
Awesome, thanks! Don't forget the gh-pages branch.
161.
by Titanous 12y ago
This is a great idea, but the "non-commercial" clause of the Creative Commons license makes the documents pretty useless as the only real use would be in a commercial context.
162.
by Titanous 12y ago
With the update installed: $ curl -s https://raw.githubusercontent.com/hannob/bashcheck/master/bashcheck | bash Not vulnerable to CVE-2014-6271 (original shellshock) Not vulnerable to CVE-2014-7169 (tav
163.
by Titanous 12y ago
The iPhone 5 doesn't have the "motion coprocessor" (added in 5S), so it's unlikely that it will gather this data without a third-party app.
164.
Twitpic is blocking the Archive Team from making an archive(twitter.com)
16 points by Titanous 12y ago|2 comments
165.
by Titanous 12y ago
Asciidoc (and the myriad of other markup languages that are supported in their file rendering) is not supported in comments/issues/pull requests, only "GitHub Flavored Markdown".
166.
by Titanous 12y ago
I have one and highly recommend it. The distro is actually Debian-based and is mostly an open source fork of Vyatta but has some proprietary bits for the Cavium offload.
167.
by Titanous 12y ago
If you have a Docker image on a registry somewhere you can create a release in Flynn from it using the `flynn release add` command (or the API).
168.
by Titanous 12y ago
We certainly not cloning Heroku's API, but we have most of the things you describe and much more in our API and CLI, including release management, configuration, job control, resource provisioning, log access, docker image releases, in
169.
by Titanous 12y ago
We can use sdutil[0] to render info from service discovery into a config template. [0] https://github.com/flynn/flynn/blob/master/sdutil/configure....
170.
by Titanous 12y ago
We're tracking this issue at https://github.com/flynn/flynn/issues/85 To date we've tried to push fixes upstream to buildpacks so that we can avoid the maintenance burden of keeping forks up-to-date
171.
by Titanous 12y ago
While Flynn is capable of a lot more, as evidenced by its architecture, leading up to the first production release we're focused on solving some of the simpler use cases really well. A solid "private Heroku" was the primary d
172.
by Titanous 12y ago
No, we have our own scheduling framework and schedulers inspired by the Google Omega paper.
173.
by Titanous 12y ago
Interesting, this looks like a fork of Ripple (and is by an original creator of Ripple).
174.
by Titanous 12y ago
No, the messages are encrypted device-to-device with Apple providing a key directory service. Apple must be complicit to read messages without physical or backdoor access to the device. http://blog.quarkslab.com/imessage-pri
175.
by Titanous 12y ago
This is almost certainly a direct response to this presentation: https://news.ycombinator.com/item?id=8057470
176.
by Titanous 12y ago
And don't forget the humans that support everything.
177.
by Titanous 12y ago
Actually I don't think the fiscal loss is so clear-cut. Each deployment of cache nodes removes load/bandwidth from the rest of the CDN, and also reduces support time spent with customers. In fact, 100% of Netflix traffic outside t
178.
by Titanous 12y ago
The new title is not more informative; "Pseudo IPv4" is a new term that is meaningless before reading the article. The original title was more informative, especially in context with the URL domain.
179.
by Titanous 12y ago
> Likewise, wrapping all the small blue 'f' icons and their associated tracking icons in TLS/SSL does not improve privacy on the net in any meaningful way. It absolutely does, global passive attackers have been documented
180.
by Titanous 12y ago
> The biggest one, in my mind, is the 'one POST per follower per message' problem. Yeah, all distributed systems must communicate with their peers. In the worst case this means sending a POST for each message to each subscriber

More ›