Just think of what would happen if an unauthenticated unprivileged user gets access to root and control of PID1 over a remote link... and you worry about an authenticated unprivileged user at the keyboard...

I think I understand the problem: a4z either does not like attacks against public individuals regardless who they are (Satya Nadella/George W. Bush) nor their projects (lets not discuss Microsoft regarding its lack of quality control, spyware, and forced updates/Iraq war), he likes Poettering, or this is triggering some psychological trauma from past experiences.

Is systemd taking the proper precautions when introducing new features? Maybe this will be a wake up call to them before something bad happens.

Ha ha no.

https://medium.com/@davidtstrauss/ho...61d#.yq0613dan
https://medium.com/@davidtstrauss/ay...4c1#.9jx9v8jrh

2 members found this post helpful.

I'm trying hard to get this thread back to the point where I don't feel I need to close it. While funny to some, do realize comments like these are not constructive, helpful, on topic and don't invite positive discussion. So don't, OK?

@All: and that goes for all of you, period.

I am sorry, I disagree but I will obey. I think understanding his motive is constructive because from what I gather he seeks to derail and close all threads on this topic by inciting flame wars, so I think unless he is going to be prevented from doing that he needs to be understood. This topic happens so infrequently that I don't understand his frustration and reading the threads is irritating because of the flame wars that erupt. I could have worded my inquiry better (should have left out the last part) but I think it is still valid and I said it with all seriousness. It wasn't meant to be funny. The first part was pretty much his own words in regard to the subject of the topic.

I think these threads need some ground rules with severe punishments if those rules are violated because this is going to happen again and again until these threads themselves are prevented from appearing otherwise. Anyway, good luck to you in your endeavor!

1 members found this post helpful.

Thanks, and I do agree: I'd say getting to learn motives is pretty much vital for understanding. Re: rewording, yes, that's basically Terry Pratchett on "the difference between using a feather and using a chicken" : - )

1 members found this post helpful.

That is called a "red herring". The existence of other bad software does not magically make systemd better. I do not believe that anyone has claimed "Oh, if only systemd could have been written as well as bind!"

The 3rd sticky thread on the top of the forum is all about security vulnerabilities in Slackware, for god's sake.

But I'll play along. In the list of bind security problems, they all appear to appear to do bad things to bind but nothing else. I didn't see where the server becomes unresponsive, reboot, slows login, etc.

2 members found this post helpful.

*If you check this list in this order then CVE-2016-2776 (2016-09-27) ranks 23rd. Almost all DoS vulns and CVE-2016-2776 should make a name server halt completely.

// I'll stop now because moderators shouldn't be posting replies in threads they moderate...

1 members found this post helpful.

LWN had a recent article on how systemd and it's 'unit' files was working out in practice. Regardless of which side of the systemd debate you stand, it's an interesting read.

http://lwn.net/Articles/701549/


Enjoy.

2 members found this post helpful.

Nah, grab a beer and have some fun with us.

and you peered into the magic 8 ball to determine my coding and sys admin abilities or just random chatter? Notice, no insults in my reply to you, so where is the hostility coming from? No reason for the thread to become about insults and exaggerations, heated debate is fine, but why the insults and slander?

2 members found this post helpful.

When I drill into CVE-2016-2776, I see where named is killed and does not recover. I do not see where the system running named is bricked.

I'm willing to believe you, but you'll have to lead me by the nose to the correct location or give me a search term to use to snuffle it out myself.

OK, I see the problem. When I said "system", I meant the linux system running on the box versus the named daemon. Those CVEs will bork bind but you can still log in and do other stuff to the linux system.

1 members found this post helpful.

To be perfectly straight-forward with you, and judging by how systemd's developers treat the project... you should decide for yourself.

However, that being said, I think at this point, if they don't start taking issues seriously and fix things before the pile of poo hits the ceiling fan and goes everywhere, they're going to be in for a nasty surprise when system administrators start dumping operating systems using systemd in favor of those that don't due to security concerns, and system developers start dumping the systemd model for the classic sysv design framework.

This isn't about Lennart's ethics any more, this is about common sense security and network practices being well ignored in favor of rampant progressivism without consequences. Relevance of modern system design be damned. This is relevance towards security and with the day and age we live in where you get attacks from countries known to sponsor and support hackers and commit cyberattacks, identity theft, and other fraud, there is no middle ground on the issue of security. Either you have proper security levels, or you don't.

1 members found this post helpful.

Provably, by this thread (just look at the begin) the psychological trauma is more on the side of the Slackware community, where several members take the first Linux experience of some person to serious and focus on the, in this context total irrelevant word Slackare.
If you would remove the word Slackware from the interview it would change nothing, and how was the reaction (see post#5).

some portion of paranoia, a common image of an enemy, taking your self to serious, bashing all that are not 100% with you as they are against you, suddenly people have an opinion just because they can run with the pack, not mentioning mods that have all the sudden a very strange view of reality and call the term 'big mouth' inappropriate language. funny looking at the post I quote here., but just on other sing for how far of reality this sect here meanwhile is.

1 members found this post helpful.

I've seen this sort of entitlement before, and I assure you nobody will fork it because there is no point forking things that have such a major defect in the blueprint.
Things that used to work but changed for the worse can get forked, but this thing was defected before it was written because of the idea to couple all the things into one PID.
It's not technical knowledge or lack thereof that prevents people from forking the project, it's the fact that it's wasted time and effort trying to improve upon a useless design.
Next time someone tells you he doesn't need or like some program, you should assume he won't use it at all, and suggest another one, not expect him to rewrite the thing just because it's open source.
And before you post more flamebait, let me remind you what happened to the old slackware forums.

1 members found this post helpful.