As long as people keep this function q is dangerous attitude, they're going to make the big mistakes- the design mistakes that aren't really fixable: Like postfix using a world-writable queue directory [...]
The only thing in a Postfix spool writable by other than the Postfix user is the maildrop queue,
which is group-writable and owned by the group that postdrop is setgid to. So, whatever problems it may have had in the past that way, they've clearly been fixed.
You might be interested in Cyclone, a safe variant of C that's influenced by ML and attempts to retain as much of the low-level control of C as it can; it uses what's called region-based memory mangement, which in theory provides useful alternatives to regular GC. (I haven't actually tried to write anything in it, though, so I can't say how practical / easy to use that kind of thing is.) MLKit does something similar, I think.
Absolutely, and they do that all the time. For example, my current phone pair was nabbed from another tenant in my building who'd cancelled their land line, apparently in favor of a cell phone. As for what happens when/if someone else moves in there and actually wants plain old telephone service... well, the repairman didn't care, because it'll probably be someone else's problem.
It doesn't replicate Opera's best porn surfing feature though, the Fast Forward button. If you go to a numbered file - say, www.somepornsite.com/images/31.jpg - and hit Fast Forward, it will automatically go to the next number in the series. Hours of fun.
I wrote that as a bookmarklet (JavaScript bookmark) for Mozilla once, and it'd probably work just as well on anything else halfway modern; it wasn't terribly hard. (Um, so to speak.)
Which, I guess goes back to the talk of Firefox having extensions and extensibility where Opera has built-in features.
Why are you not treating email as public now? Don't you realise it's not private nor confidential in any way? Why are you sending sensitive information over email presumably unencrypted?
Becuase it's one thing to be in the right place in the network with a sniffer at the right time to catch a few pieces of mail, and quite another to be able to go and get access to all of someone's stored email by filing the right form.
IOW, there's more to it than just "secure" vs. "insecure".
In C, multidimensional arrays are a fiction, because a[i][j] is given exactly the semantics of *(*(a + i) + j), instead of *(a + i * second_dim + j). That extra dereference takes away a huge number of optimization opportunities.
C does have true multidimensional arrays; you declare them like int a[32][32][32][32], rather than int ****a. They don't have a special syntax because they don't need one.
Laugh all you want, but there was a halfway serious effort at one point to see what it would take to get the Plan9 C toolchain (which is vastly simpler than GCC, although ISTR it doesn't support all of ANSI C) released under a BSD-compatible license. I think the motivation was a combination of GCC's GPL-ness and its size/complexity.
It's OmniWeb. The same thing -- the CitiBank pop-up replacing the first Secunia window (and being told I have no pop-up blocking when I do) -- happens to me with OW 5.1b4 and no proxy.
3) Prefixes for "struct" fields in standard library are redundant
They are now, but they weren't when Unix was written. For that matter, "." and "->" weren't redundant back then; there's at least one place in the Lions Book where there's an int on the left-hand side of a ".", and a few others with ints on the LHS of "->", and the meanings are different.
Also, there's an important difference between a 36-bit word-addressed system in the 60's or 70's (when disks and files were much smaller than they are now) and a 32-bit octet-addressed system today, namely that having a single file that's too big to be memory-mapped just wouldn't have happened then (I assume), but is definitely a big issue now.
With a 64-bit octet-addressed system, though, things are a little different....
Or you can have your SMTP envelope sender be whatever@my-ip-provider.net, but set the From: header to me@somewhere.edu; or, failing that, there's still the Reply-To: header.
Java is a strongly typed language therefore you have to tell the compiler exactly what you intend to use. And if you make a mistake in the way you use it, the compiler has the guts to tell you that you were wrong.
Leaving aside the fact that static typing and strong typing are not the same thing, there is more to life than FORTRAN vs. Lisp. Take, for instance, type inference --- which, at 20-odd years old, seems to be a little too cutting-edge for industry.
I seem to recall reading, a few days ago, a Gentoo security advisory about libpng, wherein was recommended upgrading to at least 1.2.5-r7, which had a fix. Was that the same bug as this?
...used to be enabled in the Mac world, until a virus went around a few years ago (pre-X) that used that feature to propagate. Now it's not. Interestingly, I don't recall ever hearing about anything similar for Windows; corporate-sponsored malware like this, yes, but not viruses.
Slashdot Mirror
Xemacs can mix text and X11 frames, IIRC. (Of course, that means using xemacs....)
As long as people keep this function q is dangerous attitude, they're going to make the big mistakes- the design mistakes that aren't really fixable: Like postfix using a world-writable queue directory [...]
The only thing in a Postfix spool writable by other than the Postfix user is the maildrop queue, which is group-writable and owned by the group that postdrop is setgid to. So, whatever problems it may have had in the past that way, they've clearly been fixed.Already taken.
If anything supported LZO, that might help with the CPU usage.
You might be interested in Cyclone, a safe variant of C that's influenced by ML and attempts to retain as much of the low-level control of C as it can; it uses what's called region-based memory mangement, which in theory provides useful alternatives to regular GC. (I haven't actually tried to write anything in it, though, so I can't say how practical / easy to use that kind of thing is.) MLKit does something similar, I think.
Absolutely, and they do that all the time. For example, my current phone pair was nabbed from another tenant in my building who'd cancelled their land line, apparently in favor of a cell phone. As for what happens when/if someone else moves in there and actually wants plain old telephone service... well, the repairman didn't care, because it'll probably be someone else's problem.
It doesn't replicate Opera's best porn surfing feature though, the Fast Forward button. If you go to a numbered file - say, www.somepornsite.com/images/31.jpg - and hit Fast Forward, it will automatically go to the next number in the series. Hours of fun.
I wrote that as a bookmarklet (JavaScript bookmark) for Mozilla once, and it'd probably work just as well on anything else halfway modern; it wasn't terribly hard. (Um, so to speak.)
Which, I guess goes back to the talk of Firefox having extensions and extensibility where Opera has built-in features.
I think you mean "welcome to the 1960's and Multics".
POVray used to be written in plain C, but recent versions -- 3.5 and later, I think -- use C++.
Why are you not treating email as public now? Don't you realise it's not private nor confidential in any way? Why are you sending sensitive information over email presumably unencrypted?
Becuase it's one thing to be in the right place in the network with a sniffer at the right time to catch a few pieces of mail, and quite another to be able to go and get access to all of someone's stored email by filing the right form.
IOW, there's more to it than just "secure" vs. "insecure".
In C, multidimensional arrays are a fiction, because a[i][j] is given exactly the semantics of *(*(a + i) + j), instead of *(a + i * second_dim + j). That extra dereference takes away a huge number of optimization opportunities.
C does have true multidimensional arrays; you declare them like int a[32][32][32][32], rather than int ****a. They don't have a special syntax because they don't need one.
Enh. I tried it for a week or two, then went back to twm.
Laugh all you want, but there was a halfway serious effort at one point to see what it would take to get the Plan9 C toolchain (which is vastly simpler than GCC, although ISTR it doesn't support all of ANSI C) released under a BSD-compatible license. I think the motivation was a combination of GCC's GPL-ness and its size/complexity.
It's OmniWeb. The same thing -- the CitiBank pop-up replacing the first Secunia window (and being told I have no pop-up blocking when I do) -- happens to me with OW 5.1b4 and no proxy.
3) Prefixes for "struct" fields in standard library are redundant
They are now, but they weren't when Unix was written. For that matter, "." and "->" weren't redundant back then; there's at least one place in the Lions Book where there's an int on the left-hand side of a ".", and a few others with ints on the LHS of "->", and the meanings are different.
Also, there's an important difference between a 36-bit word-addressed system in the 60's or 70's (when disks and files were much smaller than they are now) and a 32-bit octet-addressed system today, namely that having a single file that's too big to be memory-mapped just wouldn't have happened then (I assume), but is definitely a big issue now.
With a 64-bit octet-addressed system, though, things are a little different....
*BSD also has reboot/halt/poweroff that aren't confused as to their function the way Linux's are. But...
[On] SunOS ... [j]ust pass the appropriate option to shutdown... (-r for reboot, -p for poweroff, halt is the default)
...on BSD (well, NetBSD at least), however, it's shutdown -h for halt, and the default is to drop back to single-user. Fun, no?
We have always been at war with Oceania.
Or you can have your SMTP envelope sender be whatever@my-ip-provider.net, but set the From: header to me@somewhere.edu; or, failing that, there's still the Reply-To: header.
Java is a strongly typed language therefore you have to tell the compiler exactly what you intend to use. And if you make a mistake in the way you use it, the compiler has the guts to tell you that you were wrong.
Leaving aside the fact that static typing and strong typing are not the same thing, there is more to life than FORTRAN vs. Lisp. Take, for instance, type inference --- which, at 20-odd years old, seems to be a little too cutting-edge for industry.
Maybe someone will write a program that lets them dial up all the company's phone extensions looking for illicit modems.
Answering myself: judging by the more recent advisory, it's not, or there were more bugs than -r7 fixed, or something.
I seem to recall reading, a few days ago, a Gentoo security advisory about libpng, wherein was recommended upgrading to at least 1.2.5-r7, which had a fix. Was that the same bug as this?
...used to be enabled in the Mac world, until a virus went around a few years ago (pre-X) that used that feature to propagate. Now it's not. Interestingly, I don't recall ever hearing about anything similar for Windows; corporate-sponsored malware like this, yes, but not viruses.
Star Trek Voyager: "To boldly promote the worst captain ever! Yeah, Janeway - you go, girl. Magically know stuff that no one else does. Cool, baby!!!"
Oh, like Picard didn't do that all the time?