Not to state the obvious, but here's the definition of `overflow_ubus`
static inline bool overflow_usub(unsigned int a, unsigned int b,
unsigned int *res)
{
*res = a - b;
return *res > a ? true : false;
}
So the 2 conditionals from the patch are completely idiotic and wrong.
`overflow_ubus` not only makes an unnecessary assignment to `mtu`, but does a check after that assignment, and then you need another check for it outside of `overflow_ubus`.
In general, the proposed patch conditionals could be rewritten as
unsigned int oldmtu = mtu;
mtu -= hlen + sizeof(struct frag_hdr);
if (mtu > oldmtu || mtu <= 7)
goto fail_toobig;
First thing I did when installed Yosemite on Saturday was to disable all kinds of "nice" suggestions in Spotlight.
Second thing - Safari. I've disabled everything that has to do something with "Search" and the "new smart location bar".
Why do they still call it Flash?
It's obvious that in the near future it won't be Flash anymore, they're just trying to retain the name for obvious reasons - keep installing the Flash shit on your rig.
FWIW, I have no flashes installed 3 months now and I'm happier than ever.
Come on, guys, you'll ever only use FPU instructions when you need speed, not precision.
Anyone remember 0x5f375a86?
The precision used in Quake's source code wasn't even nearly comparable to the FPU, but was fast enough.
In other words, you'll never calculate shopping cart totals minus discounts and other stuff this way (or, at least, you shouldn't!)
There's BigDecimal in Ruby/Java, decimal.Decimal in Python, GMP in C/C++, etc...
Javascript, which is horrendously bad for large projects
A few months ago I had this project that consisted of nearly 200 controllers and 100-150 directives / modules (AngularJS)
Tell me how bad is it?
The asset pipeline compiled this to a single file in production, which was some 300K. I agree that this is a heavy load, but we're talking regular website, not a mobile one.
I think that it's not the regular water use that's the problem, but the *misuse* - mainly manual underground water extraction...
Normally, water that has come to the ocean will eventually return to the ground in the form of rain, rivers will be full, etc...
Manually extracted water could not be returned that easily to the source. I'm not aware of the way that rivers are formed, or if/how they refill but this doesn't seem to be the problem in this case.
And, uhm, yes. The ocean level is rising since I remember. Deal with it.
Twitter has filed the patent, but it's still not granted.
We'll see about this patent trolling in the near future, but my 2 cents are that Twitter will, sooner or later, start trolling around. Though I'd be happy to be proven wrong.
No you don't, they actually resolve the target links, at least for the common URL shortener services.
Well then, this gives one the opportunity to DDoS either URL shorteners or MSN servers. Imagine a 1,000,000+ shortened URLs within 5 minutes - make a HEAD request for each, now that's a flood!
How about libpeas, or something like that?
At the moment GNOME provides extending with Python, JavaScript and C via some FFI magic stuff...
I'm sure they can make something like that *if* they really decide to do it...
And, of course, this will slow down the compiler at least twice, maybe even more.
C++ is good, but C is best.
Ever wondered why the kernel is written in C (with lots of assembly spices), not C++?
Slashdot Mirror
size_t is unsigned. ssize_t is signed.
Not to state the obvious, but here's the definition of `overflow_ubus`
static inline bool overflow_usub(unsigned int a, unsigned int b,
unsigned int *res)
{
*res = a - b;
return *res > a ? true : false;
}
So the 2 conditionals from the patch are completely idiotic and wrong.
`overflow_ubus` not only makes an unnecessary assignment to `mtu`, but does a check after that assignment, and then you need another check for it outside of `overflow_ubus`.
In general, the proposed patch conditionals could be rewritten as
unsigned int oldmtu = mtu;
mtu -= hlen + sizeof(struct frag_hdr);
if (mtu > oldmtu || mtu <= 7)
goto fail_toobig;
Now that's ugly!
99 little bugs in the code,
99 little bugs in the code.
Take one down, patch it around.
127 little bugs in the code.
Anyone read the article?
The vulnerability is only exploitable when fetching an FTP directory, recursively, from a malicious server.
Yeah, it's a hole, but it's not shellshock. Stop bitching around and just update your box.
First thing I did when installed Yosemite on Saturday was to disable all kinds of "nice" suggestions in Spotlight.
Second thing - Safari. I've disabled everything that has to do something with "Search" and the "new smart location bar".
Why do they still call it Flash?
It's obvious that in the near future it won't be Flash anymore, they're just trying to retain the name for obvious reasons - keep installing the Flash shit on your rig.
FWIW, I have no flashes installed 3 months now and I'm happier than ever.
Come on, guys, you'll ever only use FPU instructions when you need speed, not precision.
Anyone remember 0x5f375a86?
The precision used in Quake's source code wasn't even nearly comparable to the FPU, but was fast enough.
In other words, you'll never calculate shopping cart totals minus discounts and other stuff this way (or, at least, you shouldn't!)
There's BigDecimal in Ruby/Java, decimal.Decimal in Python, GMP in C/C++, etc...
A few months ago I had this project that consisted of nearly 200 controllers and 100-150 directives / modules (AngularJS)
Tell me how bad is it?
The asset pipeline compiled this to a single file in production, which was some 300K. I agree that this is a heavy load, but we're talking regular website, not a mobile one.
Fuck this shit. I'm still playing Super Mario on my 8-bit Nintendo!
It's reasons like this I refuse to install any closed source binaries - besides the inbound and outbound firewall...
I think that it's not the regular water use that's the problem, but the *misuse* - mainly manual underground water extraction...
Normally, water that has come to the ocean will eventually return to the ground in the form of rain, rivers will be full, etc...
Manually extracted water could not be returned that easily to the source. I'm not aware of the way that rivers are formed, or if/how they refill but this doesn't seem to be the problem in this case.
And, uhm, yes. The ocean level is rising since I remember. Deal with it.
So, M$ are urging people to order, respectively buy Win7's 'till 1st of July, so they can release Win8 in August...
Nice!
Twitter has filed the patent, but it's still not granted.
We'll see about this patent trolling in the near future, but my 2 cents are that Twitter will, sooner or later, start trolling around. Though I'd be happy to be proven wrong.
It was clear that RIM doesn't go well after Halliburton ditched BlackBerries for iOS.
From my point of view, I won't miss them at all.
No you don't, they actually resolve the target links, at least for the common URL shortener services.
Well then, this gives one the opportunity to DDoS either URL shorteners or MSN servers. Imagine a 1,000,000+ shortened URLs within 5 minutes - make a HEAD request for each, now that's a flood!
So they block URLs, marking them as spam. Use a URL shortener, like t.co / bit.ly / what.ever, so you can bypass the scheme.
How about libpeas, or something like that?
At the moment GNOME provides extending with Python, JavaScript and C via some FFI magic stuff...
I'm sure they can make something like that *if* they really decide to do it...
Yeah, Chrome attempts to bring ActiveX back!
I just wonder when will M$ get consumed by Google and they turn "evil".
I don't know if she survives, yet I was born ~25 days prematurely.
It's still very impressive, though.
And, of course, this will slow down the compiler at least twice, maybe even more.
C++ is good, but C is best. Ever wondered why the kernel is written in C (with lots of assembly spices), not C++?