When 1) complex computer programs become mathematically provable, and 2) computer languages become complex enough to convey proper meaning, then writing becomes obsolete (because documentation will just be a question of running the program through the checker). And not before, in my neck of the woods. Oh, and the solving of both issues is a lot further away than 2020 by any estimate.
What the hell is that all about? I rather like the idea of being able to board an aircraft and not have any problems because some yokel with too much money decides it's fun to fly a piece of plastic into the engine of my plane. Please FAA - keep on fining!
The cool kids jumped on the python bandwagon saying perl was old, but in all this time they have yet failed to: - created a language that has libraries like perl has, - created a scripting language that can execute sql safely like perl can, - created a language that has regular expression support as part of the syntax (so you don't have to enter in yet another level of indirection and escape all the whatevers ' " \ / when you're trying to simply match some string easily), - created a scripting language that is also fast.
It's already established that people circumvent airgaps by raising temperatures of the one machine, and detecting it by the other. Or by using audio and microphones.
Sorry, but if ads were simply generated on the webserver itself (in case of slashdot), with images that also come from slashdot itself, or - in case of something like wordfeud - the ads are simply proxied by the app's home base (apps also phone home for stuff, right?), then the ad-traffic becomes indistinguishable from other, necessary traffic and ad-blockers would be out of work, right?
Yet this doesn't happen. So apparently, it is still too easy to serve apps.
It's a privilege escalation inside a very complex environment. Su is a simple shell interface to a system call.
I'll tell you what - as long as I can turn the option of escalation privilege to arbitrary processes off inside systemd, in a safe and predictable manner, and the option to turn it off is heavily documented, I'm happy.
Su is not a broken concept; it's a long well-established fundamental of BSD Unix/Linux.
You're pretty much making an argument to tradition here. The correct thing to do would be to counter his claims:
what "su" is supposed to do is very unclear. On one hand it's supposed to open a new session and change a number of execution context parameters (`uid`, `gid`, `env`,...), and on the other it's supposed to inherit a lot concepts from the originating session (`tty`, `cgroup`, `audit`,...). Since this is so weakly defined it's a really weird mix&match of old and new paramters.
I would like more detail from him on why and how it's broken, and how his replacement is truly different from "su -" but since it doesn't appear to be mutually exclusive with the use of "su" or "su -", other than typical reactionary hate I don't see what the problem is.
99% of the execution context changes and things that stay the same that su cause, happen in any subshell. Does Poettering dislike subshells as well? Does he dislike shell scripts?
It must be cool to have a job. A closely knit society, where every member is confronted with the question: 'so, what do you do for a living?' every now and again. And if the answer is, 'I'm on basic income, always have been', then you're simply considered uninteresting to talk to.
Servers process enormous amounts of data that could increase the entropy pool. Although they can be manipulated to some extent, the timing and content of network packets that reach them can hardly be predicted.
Exactly. There is one big danger in programming and that is... well, there are *two* big dangers in programming and those are... Anyway, *amongst* the biggest dangers in programming we find the problem of parsing. Combine things like BER encoding (responsible for such wonderful not-at-all critical things like SNMP and X509), and languages like C (I absolutely love C, mind) and well.. you have the cocktail you have today. No, but absolutely not a single language at all took the hint from perl and made a semantic description of a parsing problem a core primitive of a computer language. They should have - I absolutely *crave* a compiled system-language that can do what perl can do with regexes and string-packing.
As someone who has been, albeit unwittingly, at the receiving end of a 'FOIA' request (they call it 'WOB' in my country), I say: good. These requests aren't here so that journalists can make a buck. They are here so that the public knows what's going on inside government. So while I was going to have my conversations with some civil servant exposed, I wasn't allowed to know which fucker made the requests. I say: if you wanna be a big boy, you aren't afraid to show who you are. You shitty journalists stand up for yourself.
Sorry about the rant. I just got to my deepest nerves at the time.
And part of being even older than you, is to realize that promising revolutions is just a human way of saying: I've achieved something. And then we shake our weary, old heads, and we applaud the youngster for his work. And then it's nap time.
Slashdot Mirror
When 1) complex computer programs become mathematically provable, and 2) computer languages become complex enough to convey proper meaning, then writing becomes obsolete (because documentation will just be a question of running the program through the checker). And not before, in my neck of the woods. Oh, and the solving of both issues is a lot further away than 2020 by any estimate.
say 'Hello apocalypse!';
What the hell is that all about? I rather like the idea of being able to board an aircraft and not have any problems because some yokel with too much money decides it's fun to fly a piece of plastic into the engine of my plane. Please FAA - keep on fining!
The cool kids jumped on the python bandwagon saying perl was old, but in all this time they have yet failed to:
- created a language that has libraries like perl has,
- created a scripting language that can execute sql safely like perl can,
- created a language that has regular expression support as part of the syntax (so you don't have to enter in yet another level of indirection and escape all the whatevers ' " \ / when you're trying to simply match some string easily),
- created a scripting language that is also fast.
Which are all the reasons I love and use perl.
Almost never used it, and they're about to learn a hard, hard lesson.
It's already established that people circumvent airgaps by raising temperatures of the one machine, and detecting it by the other. Or by using audio and microphones.
a) In proper security devices the security logic doesn't execute within the same unit as the rest of the compromised device.
b) this isn't about people breaking firewalls. It's about people trying to break data diodes.
Throughput is different from latency, you know.
But really, if there were aliens out there advanced enough to pick up our signals, they'd be advanced enough to crack our crypto.
'serve apps' must be 'serve ads'.
Sorry, but if ads were simply generated on the webserver itself (in case of slashdot), with images that also come from slashdot itself, or - in case of something like wordfeud - the ads are simply proxied by the app's home base (apps also phone home for stuff, right?), then the ad-traffic becomes indistinguishable from other, necessary traffic and ad-blockers would be out of work, right?
Yet this doesn't happen. So apparently, it is still too easy to serve apps.
'The cloud' is also a backup facility. For those not-so-small companies.
It's a privilege escalation inside a very complex environment. Su is a simple shell interface to a system call.
I'll tell you what - as long as I can turn the option of escalation privilege to arbitrary processes off inside systemd, in a safe and predictable manner, and the option to turn it off is heavily documented, I'm happy.
The problem is at step 5): su isn't confusing. It's a lame excuse to get your way.
You're pretty much making an argument to tradition here. The correct thing to do would be to counter his claims:
I would like more detail from him on why and how it's broken, and how his replacement is truly different from "su -" but since it doesn't appear to be mutually exclusive with the use of "su" or "su -", other than typical reactionary hate I don't see what the problem is.
99% of the execution context changes and things that stay the same that su cause, happen in any subshell. Does Poettering dislike subshells as well? Does he dislike shell scripts?
Ok. Do you want someone to be able to break out of a chroot or jail, using [alternativetosu] ? Because you might not want that...
It must be cool to have a job. A closely knit society, where every member is confronted with the question: 'so, what do you do for a living?' every now and again. And if the answer is, 'I'm on basic income, always have been', then you're simply considered uninteresting to talk to.
"If you are living in another EU country, your employment and tax data is available to the government of Finland."
In theory, yes. What does it cost to bribe a Croatian official?
Did they find the guy who leaked the information?
Servers process enormous amounts of data that could increase the entropy pool. Although they can be manipulated to some extent, the timing and content of network packets that reach them can hardly be predicted.
Exactly. There is one big danger in programming and that is... well, there are *two* big dangers in programming and those are... Anyway, *amongst* the biggest dangers in programming we find the problem of parsing. Combine things like BER encoding (responsible for such wonderful not-at-all critical things like SNMP and X509), and languages like C (I absolutely love C, mind) and well.. you have the cocktail you have today. No, but absolutely not a single language at all took the hint from perl and made a semantic description of a parsing problem a core primitive of a computer language. They should have - I absolutely *crave* a compiled system-language that can do what perl can do with regexes and string-packing.
As someone who has been, albeit unwittingly, at the receiving end of a 'FOIA' request (they call it 'WOB' in my country), I say: good. These requests aren't here so that journalists can make a buck. They are here so that the public knows what's going on inside government. So while I was going to have my conversations with some civil servant exposed, I wasn't allowed to know which fucker made the requests. I say: if you wanna be a big boy, you aren't afraid to show who you are. You shitty journalists stand up for yourself.
Sorry about the rant. I just got to my deepest nerves at the time.
And part of being even older than you, is to realize that promising revolutions is just a human way of saying: I've achieved something. And then we shake our weary, old heads, and we applaud the youngster for his work. And then it's nap time.
Linus Torvalds himself created, and then ported to jQuery, the entire kernel source code. Or so I've heard.
This is like a virtual machine for all instances of strcmp?
I'm not sure, but your vibrator doesn't have feelings, I think.