i was thinking the last six months to a year, actually, and this research and/or similar information really has been all over the international BBC feeds for at least that long.
i don't even know what asinine means, let alone OP, but i do not get the impression you are being very polite.
i've done more harm to my own (and other people's) code by following advice taken from MSDN articles than by any another means.
microsoft have a way of breaking everything, and then writing about it is if they invented the solution.
except their solutions never work.
the number of times i have had to rewrite server code, socket code, locking code, threading code, all because the original was based on one of their samples.
there is no single "right" way to write code, but there are plenty of wrong ones, and microsoft have been the worst offenders, to date, in my experience.
at time of writing stackoverflow is my best reference, and otherwise plenty of RTFM.
plastic footed metal beetle space bugs, smell of laboratories, and live on soap.
is good to be human, in the information age, and i do hope these strange offspring of the petrochemical age die off soon..
yes, this is flame bait, however i am making the point that it is also further evidence that we have a problem, and this is news that matters, however many cannot handle that information.
we now live in a world where the car kills more children than anything else, and i don't know about you, but according to the real live property laws in the land where i live, the ONLY allotted space for pedestrians is a strip one and a half meters wide ALONGSIDE the edge of the highway.
there is literally no other legal way to get from one place to another, entirely everywhere else is property.
mad, quite mad - the whole plastic footed metal space bug lot of you.
i have kinetic memory, my body knows where it put something, even when i cannot remember a thing.
there is no substitute for writing it down, i find, and typing is definitely not writing, does not have the same effect.
the only digital solution that almost worked for me was a pen tablet, and perhaps now that our invention has come full circle, and we're back to scribbling on stone (well, sand) tablets again, i may finally lose the pen and paper..
but not yet - paper can be recycled - and as far as i know this is not true for batteries.
my "unwilling to wade in the bulls" take on this affair is that some part of ssl on the outward face of that service is bleeding large chunks of raw memory, in response to a trivial attack.
i'm not clear on on is which parts of memory are bleeding..
only ssl services memory?
or all memory from all services in the vicinity?
or all memory in general?
i'm hearing that sll privates are amonst the things that are leaking, but can anyone please clearly define which parts of my various systems have been wide open to the world, these past two years and more?
some people are saying ssh is not affected..
this is important to me - i don't care about ssl, and consider the bulk of the applications it supports to be trivial, but i cannot work without ssh, and am not aware of any viable alternatives.
i've always assumed that ssh was built on top of ssl - as in why reinvent the wheel - but when i went digging, trying to sort out which versions i have been running, and what i need to update, etc, i seem to be finding that ssh is actually standalone, apparently?
perhaps built on similar principles, but by differerent groups, and never merged - or do i have a bent picture?
apparently i need to learn more about these things - in matters like this i prefer to be able to read the source than listen to pundits pound the keys..
i am one, so i know, don't argue with me.
anyway - hello - if anyone can please enlighten or point at the histories of both open ssl and ssh for me, it would be a great help,
and if anyone could please point at, or repeat the answer to my question about what exactly has been exposed - thank you.
the plaintiff in this case appears to be going after "damages" - as if his right to make similar "jealous" profit from his work had been contravened.
however, under GPL - by my reading - the plaintiff has no right to claim "damages" in the "shekels" sense at all.
therefore i claim he makes a mockery of the whole point of the GPL.
he should be suing to have the V3 source released to the public, not to be released to him in order that that he can pursue his claim for a share in the "profits".
Slashdot Mirror
i was thinking the last six months to a year, actually, and this research and/or similar information really has been all over the international BBC feeds for at least that long.
i don't even know what asinine means, let alone OP, but i do not get the impression you are being very polite.
i've done more harm to my own (and other people's) code by following advice taken from MSDN articles than by any another means.
microsoft have a way of breaking everything, and then writing about it is if they invented the solution.
except their solutions never work.
the number of times i have had to rewrite server code, socket code, locking code, threading code, all because the original was based on one of their samples.
there is no single "right" way to write code, but there are plenty of wrong ones, and microsoft have been the worst offenders, to date, in my experience.
at time of writing stackoverflow is my best reference, and otherwise plenty of RTFM.
has been all over the papers the past two years, almost, outside northa merkin land..
you need to put these things together, sometimes, i think.
who is git, and to what is s/he objecting?
proves my point.
- or should be - long live the open alts.
seem to feel threatened by this information.
plastic footed metal beetle space bugs, smell of laboratories, and live on soap.
is good to be human, in the information age, and i do hope these strange offspring of the petrochemical age die off soon..
yes, this is flame bait, however i am making the point that it is also further evidence that we have a problem, and this is news that matters, however many cannot handle that information.
kids die getting hit, please get OUT from behind the windshield, step away from the weapon, space bug.
and i will build for you a live band in kernel space.
we now live in a world where the car kills more children than anything else, and i don't know about you, but according to the real live property laws in the land where i live, the ONLY allotted space for pedestrians is a strip one and a half meters wide ALONGSIDE the edge of the highway.
there is literally no other legal way to get from one place to another, entirely everywhere else is property.
mad, quite mad - the whole plastic footed metal space bug lot of you.
as proof, and thank you for the up.
i have kinetic memory, my body knows where it put something, even when i cannot remember a thing.
there is no substitute for writing it down, i find, and typing is definitely not writing, does not have the same effect.
the only digital solution that almost worked for me was a pen tablet, and perhaps now that our invention has come full circle, and we're back to scribbling on stone (well, sand) tablets again, i may finally lose the pen and paper..
but not yet - paper can be recycled - and as far as i know this is not true for batteries.
my "unwilling to wade in the bulls" take on this affair is that some part of ssl on the outward face of that service is bleeding large chunks of raw memory, in response to a trivial attack.
i'm not clear on on is which parts of memory are bleeding..
only ssl services memory?
or all memory from all services in the vicinity?
or all memory in general?
i'm hearing that sll privates are amonst the things that are leaking, but can anyone please clearly define which parts of my various systems have been wide open to the world, these past two years and more?
some people are saying ssh is not affected..
this is important to me - i don't care about ssl, and consider the bulk of the applications it supports to be trivial, but i cannot work without ssh, and am not aware of any viable alternatives.
i've always assumed that ssh was built on top of ssl - as in why reinvent the wheel - but when i went digging, trying to sort out which versions i have been running, and what i need to update, etc, i seem to be finding that ssh is actually standalone, apparently?
perhaps built on similar principles, but by differerent groups, and never merged - or do i have a bent picture?
apparently i need to learn more about these things - in matters like this i prefer to be able to read the source than listen to pundits pound the keys..
i am one, so i know, don't argue with me.
anyway - hello - if anyone can please enlighten or point at the histories of both open ssl and ssh for me, it would be a great help,
and if anyone could please point at, or repeat the answer to my question about what exactly has been exposed - thank you.
enough said.
n/t
don't have a very good track record, at the moment.
thank you - i may not like what you are saying, but it makes sense.
"you'll like this.. not a lot, but you'll like it" -- Paul Daniels
is the algorithm that counts, not the name you stick on it - you may as well try patent the word "glass" - and enjoy the karmic consequence.
the plaintiff in this case appears to be going after "damages" - as if his right to make similar "jealous" profit from his work had been contravened.
however, under GPL - by my reading - the plaintiff has no right to claim "damages" in the "shekels" sense at all.
therefore i claim he makes a mockery of the whole point of the GPL.
he should be suing to have the V3 source released to the public, not to be released to him in order that that he can pursue his claim for a share in the "profits".
what value would the method instances be?
surely any sensible rewrite would export the identical methods?
how is this any clue as to the code behind the methods exported?
i call hot air, your posts are misleading.
the GPL is about ANTI copyright.
now here is a man demanding money because he claims his GPL has been stolen.
this is a CONTRADICTION
if he were demanding that the owner (now google) PUBLISH the new version under GPL then it would be different.
if all he wants is money then i hope the sharks eat him, and they probably will, and good riddance.
this matter is a tawdry waste of the whole GPL ethic, in my opinion.
please forgive my SHOUTING, i am upset by this.
i doubt your theory would have much practical application here..
thank you and the horse you rode in on for the most useful news i've had here in a while.
gnome is driving me nuttier than i thought i could get at the moment, but am sticking with it, is better than nothing.
which about sums up the alternatives, when they're not trying to be everything.
-- dear linus, who is git, and to what is he objecting? --
what brad says is good enough for me.