_yy

Maybe it's bad design, then?

I have one of those. Root password is "juantech". Did not know about the shell, how useful! The telnet daemon crashed quickly on mine last time I played with it.

... :-/

Fortunately, I disconnected it from the network a long time ago. Works well standalone, the UI is ok.

Same for me.

> I recently adapted a colleague's document from LaTeX and it was simply easier to redraw a slightly complex table in LyX than to understand the table markup. I think he'd be disheartened to learn how fast it was to produce the table.

Can't you even import some of those?

Nice. It has an WYSIWYG editor for vector graphics.

It's confusing as hell, though.

If you like this, also take a look at RethinkDB: https://www.rethinkdb.com/

Nice project! Even if you believe that systemd is too complicated, it's a great example on how to build an asynchronous, modern init system. Upstart uses some highly questionable tricks (ptrace!) to track processes across forks whereas systemd uses cgroups.

No, you update the shared library using your distribution's package manager and then restart the affected services using one of the small scripts for that purpose.

What's the issue with that?

Sure but that's one of the reasons I use Linux.

Yes but still. If you have a procedure in place to recompile and redeploy everything, you could just deploy the libraries as well.

That's why Debian Stable and RHEL exist. Security patches don't break the API.

Remember that critical Go security update?

Usual procedure - update the shared library, restart affected services. Go - recompile everything.

You don't even have to copy the installer, you can just copy an existing install in-place (just as you'd copy an image to a Raspberry Pi SD card).

> It's inelegant, to say the very least, but it works just fine! I'm pretty sure I saw that technique used a few times during Twitch Installs Arch Linux, during the more exotic segments when some joker hijacked the effort temporarily by installing Windows 95, and TempleOS, and so on.

Don't forget Gentoo! That's precisely how they installed it.

> The stable release has full support for Python 3.5, including the new async and await functions. So recent releases can pronounce it as fully supported which was quite a feat.

Wow. That is amazing! Pyston only supports Python 2 and PyPy is working on it.

Nuitka looks very promising.

Yes - though there's more to a SSH session than executing commands (interacting with interactive editors, port forwarding, etc.)

Incident response. When one of your admin accounts is compromised, you'd want to know what the attacker executed.

Is Slack really the right place for security-critical notifications?

The Phacility guys know how to PHP. They used to work at Facebook. I don't like PHP either, but I trust the developers in this case.

Gitlab had its fair share of vulnerabilities, too, despite being written in Ruby. It's about the developers, not the language.

Have a look at their bug bounty program: https://hackerone.com/phabricator

> Also, do they pride themselves for writing this in PHP? I consider this an anti-feature, but this might be highly opinionated.

I'd prefer it to be written in something else, too, but - the Phacility team are ex-Facebook developers. If anyone knows how to use PHP, it's them. They built their own, extensive web application framework on top of it (which is a remarkable achievement for itself). Phabricator is one of those rare examples that you can, in fact, write excellent code in PHP.

On top of that, they're running a bug bounty with generous payouts: https://hackerone.com/phabricator

> 1. Phabricator is actually a suite of different applications that do specific things (e.g. source code hosting, issue tracking, project management, ...). Although Phabricator ticked all our feature boxes, some of the components it ships with are very immature and/or don't get a lot of attention from the development team.

The features which aren't explicitly marked "experimental" work very, very well in my experience. Especially the code review part, which I find more pleasant to use than Gerrit.

> 2. For some reason the platform as a whole feels like a CRUD layer on top of a data model. The UI and various workflows in the applications are very tightly coupled with the underlying data model. I guess that makes it easy to develop and maintain the various core applications of Phabricator, but it doesn't make for a very user-friendly or usable product.

Have you got some examples? They're hiding the database pretty well IMO, and we haven't had many usability complaints that weren't about minor issues. Many of the experimental features are cumbersome to use though and we've turned off some of them again to avoid confusion.

> 3. We have ~150 internal repositories, we actively work on ~40 of them at any given time. The source code application doesn't seem intended for that many repositories (e.g. navigating to a specific repository is non-trivial)

Have you raised an issue about this? They're very responsive to issues encountered in real-world use and usually decide about feature requests by user demand. I do know that they're working on improving this - the "callsigns" will become optional, for example.

> 4. Phabricator has a fundamentally different approach to "pull requests". It works really nice, but only if you commit to using the Phabricator Way Of Doing Things. However, our team has been working on Github.com for years, and we're so used to the Github-workflow that we couldn't get used to the Phabricator workflow.

Their way of doing (or actually, not doing) pull requests is the most important feature of Phabricator. Their approach scales much better than the traditional style and is - in my opinion - the most important reason to choose Phabricator over Github-style tools. This might not matter for small projects, but in a company, it sure does.

Someone wrote it up quite nicely there: http://cramer.io/2014/05/03/on-pull-requests/

Meanwhile, Phabricator has implemented all of these (and even more).

Custom templates: https://secure.phabricator.com/book/phabricator/article/form...

Votes: https://www.mediawiki.org/wiki/Phabricator/Tokens

It's better in almost every aspect than GitLab and GitHub.

See https://en.wikipedia.org/wiki/Phabricator for an (incomplete) list of open source projects using it.

Yeah but no sane organization is going to do that. It would create so much headache.

SCP/SFTP is actually a separate binary.

PuTTY is definitely not affected since it has its own SSH implementation.

Probably not. All of the big vendors use some sort of hardware acceleration to achieve >= 10gb.

There's some progress, though (like PF_RING in Linux and netmap on FreeBSD).

No such thing as session synchronization for different vendors. You also need to configure everything for both of these vendors, which may or may not have equal feature sets.

The Silver Searcher, or ag: https://github.com/ggreer/the_silver_searcher

Designed as a replacement for all of the use cases of Ack. Is even faster.

Which is really annoying, too, since there's no configurable IPv6 firewall (it's either on or off). But at least they do use IPv6.

Unitymedia, a huge German ISP, has been running dual stack for a few years now.

> Can you run docker containers in userspace?

Yes, and it increases the attack surface even more in some scenarios. Now, an unprivileged user can create new namespaces and do all sorts of things which were previously limited to root.

With "clear containers" (very minimal KVM VMs), you get the overhead down to <20MB:

https://lwn.net/Articles/644675/

Also, RAM is cheap.