There's a company in Nebraska that makes custom vending machines. One of the advantages of the disposable-phone approach is that you wouldn't necessarily have to negotiate contracts with a peppy salesperson. Just swipe your card, choose your model, and you're on your way. Are the phone sales jobs good for the economy? My inclination is to put those people to work designing a better vending experience.
So when will someone put up a $250,000 for a judge/jury who will convict Microsoft for their irresonsibility and gross negligence in propagating non permissions-based filesystems across the entire network and creating the only software ecosystem in which viruses can exist and flourish? The rise of Microsoft is the apparently the concomitant with the death of personal responsibility. Not trying to flame here folks, just an opinion formed from a life lived on Unix/Linux/Irix/BSD/OSX systems and never having had to remove a virus even once. Am I alone in thinking that Microsoft is responsible for those viruses more than the virus writers are? The fact that I unwillingly support MCSE's who make virus removal a full-time job on my tax dollar while unix talent goes neglected and left useless to novel corporate agendas has nothing to do with this bitterness. Nope. It's Microsoft's own incompetence that deserves the bounty.
Not sure about you but the first thing I thought of when reading this headline was that it applies to the RedHerring's mode(s) of commucation as well. phphhhhht! What was that? Smells like a money-grubbing silicon valley "journalist"-come-lately to me.
Although the post by Emmanual Dreyfus indicates that XDarwin is essentially a test case, this is a rather important test case. If you can run XDarwin, you're just a short hop away from having all of the X11 apps along with it. Also, imagine a package system like the fink working equally well on OSX and NetBSD. You could develop on OSX with its comfortable GUI and deploy to NetBSD with its comfortable price.
1. Even the N.Y. times wasn't able to offer much real evidence for merger talks. Also, remember that they are just talks, and a preference for IPO was stated by the company.
2. If Microsoft acquires Google, give them enough time and they will commercialize it to the point that it isn't as useful. At that point, the private world will once again rise up to meet the demand.
The real underlying conflict here is between privately and publicly owned business. The mass markets and finely tuned product quality have always been at odds.
BlueFish has occupied this space for quite some time. The spin is vintage Michael Roberson of course. We've been here before, people. He's an early adopter with a megaphone that's twice the size of yours. After all, HE KNEW ABOUT MP3 BEFORE YOU DID.
There are times I'd really wish that the tech media would genuinely research the subject matter instead of just amplifying hype. Hard-working, often-silent open source incumbent projects deserve nothing less.
Is it just me or is that Aqua-style X slashdot story icon looking outdated? What's needed is a metallic-style Panther X icon. Does Slashdot have a graphics-submission procedure? The XIcons site has a few that should work.
Here's a plausible scenario: Mr. RemainNameless stumbles across a major sql injection vulnerability while browsing a WidgetCompany's site. He realizes that WidgetCompany now has his originating IP# and ISP information in their web server log files and could track him down to accuse him of an attack on their server. What to do? If he comes forward, they can accuse of him of an attack. If he remains silent, the problem isn't fixed, and he might (especially if he is a security professional) be in trouble for not alerting anyone about this vulnerability, and there is record in the log files that he knew about it.
What's the best way to go about disclosing to a company that their network presence is vulnerable? What are the legal ramifications of doing so?
There's this little aluminum products manufacturing facility in rural Nebraska that makes great stuff for data centers, and the cost will pleasantly suprise you: www.mtpartners.com
Also, put the cables under your tiled floor, not in overhead racks. Typical overhead racks are open-air and human-accessible in a way in which tiled-in areas are not.
Finally, have someone skilled in the arts of physical security take a look at your building, entrance, etc. For example, I've seen people build really nice data centers about ten feet away from a busy road. They are unwittingly about one violent car wreck away from having their whole enterprise go down. Sure, there are concrete barriers for that sort of thing, but in both software and hardware, the best security is built in, and planned for from the beginning.
The STEAL lab at the Nebraska University Consortium of Information Assurance has a pretty nice setup that sounds similar to what the AskSlashdot post described. One thing I noticed when walking by the lab: they have signs up indicating that if you walk in through their door with a USB keydrive or a CDR, you can plan on walking out without it. The basic idea is that no electronic media, whatsoever, is allowed in or out without a CAREFUL audit of what's going on. If you're going to play with live viruses, the setup demands nothing less, I suppose. Remember that if you don't have physical security, network security doesn't make any difference.
The GIMP has a pretty robust featureset and you can download it for Linux or buy it for Win32 or the Mac.
rudimentary CMYK separation also
on
GIMP goes SVG
·
· Score: 3, Informative
There is also a rudimentary plugin now which handles CMYK color separations here. Also, the MacGIMP site had a story on the SVG changes as well before it was posted on Slashdot.
For the past three years or so, the spammers haven't caught on to this, and they are unlikely to do so given the few people who take the effort to put this measure into place.
P.S. It's not just mailto links that are being harvested here. They'll scrape anything with an @ or a "at" or...
If you're running a mail server with, say, 250 people doing what you're doing, the spam connections might very well denial-of-service your mail server, assuming it is running on a typical T1. The expense of bandwidth, not to mention the inconvenience of less-reliable mail, is what leads sysadmins and the companies who employ them to take email obfuscation seriously.
There are people in the public relations world who drool over the possibility of having the world sit around and chat about your logo redesign. This is news for nerds. Apple has had their ten minutes of fame, now it is time for open source to shine. Would a redesigned Debian logo get coverage on slashdot? It shouldn't. The avoidance of mass-commercialism led me to slashdot and now it is driving me away.
I had a nice morse code response here, but the slashdot lameness filter won't let me post it. Talk about lame. "Reason: Please use fewer 'junk' characters." I'll readily admit that ASCII graffiti is junk, but morse code? C'mon!;)
Yes, the difference between what verisign has started doing and what the domain name purveyors do is this: instead of just redirecting purchased domain names which have yet to be "pointed to" an IP#, they are redirecting any request for any domain name, in realtime that isn't already registered by use of a wildcard redirect, and furthermore, they are tracking the number of occurrances and origin of these requests with Overture web-bugs. This is a major privacy concern in addition to taking advantage of anyone who places trust in the the domain name architecture to look for a destination site.
1. The distributed network in its infancy is lovingly brought to life by researchers: arpanet is born. 2. Rapid protocol development as the network begins to start walking: from gopher to httpd to mosaic. Email and usenet populate most universities. 3. Private enterprise realize the potential and small companies start forming around services and products aimed at network usage. Network usage is a daily exercise for academics and early adopters. Linux arrives and Slashdot's squeaky pubescent voice first heard. 4. The internet meets the economy and Wall Street goes apeshit. Billion dollar companies are started, sustained, and identified by their position on the network and mindshare of net users. The network is the computer. 5. Infrastructure buildout is complete, and educated people worldwide use it as a communication medium. Initial high-growth opportunities are gone so Wall Street sours on the newness, returning its attention to fundamentals of profit-grubbing. 6. Annoying spammers take over, search engines are all manipulated, pop-ups for porn and travel are everywhere, Microsoft mass-marketed virus hysteria takes place, simple hosting efforts become a bitch. 7. Lawyers and short-sighted opportunists inexorably and slowly strip everything likeable from the network by lawmaking and lawsuits until there is nothing left but death and taxes.
Shakespeare's As You Like It (Act 2:7)...man in his time plays many parts, His acts being seven ages. At first the infant, Mewling and puking in the nurse's arms. And then the whining school-boy, with his satchel And shining morning face, creeping like snail Unwillingly to school. And then the lover, Sighing like furnace, with a woeful ballad Made to his mistress' eyebrow. Then a soldier, Full of strange oaths and bearded like the pard, Jealous in honour, sudden and quick in quarrel, Seeking the bubble reputation Even in the cannon's mouth. And then the justice, In fair round belly with good capon lined, With eyes severe and beard of formal cut, Full of wise saws and modern instances; And so he plays his part. The sixth age shifts Into the lean and slipper'd pantaloon, With spectacles on nose and pouch on side, His youthful hose, well saved, a world too wide For his shrunk shank; and his big manly voice, Turning again toward childish treble, pipes And whistles in his sound. Last scene of all, That ends this strange eventful history, Is second childishness and mere oblivion, Sans teeth, sans eyes, sans taste, sans everything.
I was in Boston at the time and missed a chance to meet you at your talk at Brookhaven Lab in New York, a year or two before the Red Hat IPO. Now RedHat seems to be well on its way to be what Wall Street identifies with as a dominant Linux company. This took about four years to accomplish, which is pretty impressive in the grand scheme of things. A lot has changed since then. If you were now in your late twenties or early thirties and wanting to bootstrap a long-term business, what would you be work on?
So now all of those wild-eyed grassroots Darwin users can rush out to download the source and compile. But seriously, in the rush to legitimize MacOSX to the GNU crowd, what happened to "stuff that matters"?
I can't speak for whoever is moderating my comments, but I from where I'm sitting this is not a blind hatred for Microsoft. It is absolutely a blind hatred for anyone wasting my tax dollars who shrugs off accountability.
Between procmail, spamassassin, bogofilter, mime defang, and any number of freely available solutions to the spam and virus epidemics, the *nix MTA problem set has a number of very effective low cost solutions ready to go. A sysadmin familiar with any scripting language (perl,bash,csh,etc) can script the patches to fix an arbitrary number of remote servers in short order. And do it securely!
I've recently heard a number of Windows/Exchange admins from different companies complaining about having to go from desk to desk, from seat to seat, from box to box applying patches which can't be scripted.
The thing about all those openssh patches is that I can control the patching mechanism itself in ways that MCSE's could only dream about. I desperately want the U.S. government to have full advantage of this efficiency instead of purchasing Symantec virus subscriptions at top dollar and then billing me next tax season for the self-congratulated job well done.
Your point about competent administration is well taken. Hopefully my point about technology tax dollars accountability will be too.
It's called a header redirect, folks. In one line of php, do:
header ("Location: http://www.newsite.com/over_here.html");
Most if not all of the traveling tech jobs I was aware of disappeared around 9/11/01.
There's a company in Nebraska that makes custom vending machines. One of the advantages of the disposable-phone approach is that you wouldn't necessarily have to negotiate contracts with a peppy salesperson. Just swipe your card, choose your model, and you're on your way. Are the phone sales jobs good for the economy? My inclination is to put those people to work designing a better vending experience.
So when will someone put up a $250,000 for a judge /jury who will convict Microsoft for their irresonsibility and gross negligence in propagating non permissions-based filesystems across the entire network and creating the only software ecosystem in which viruses can exist and flourish? The rise of Microsoft is the apparently the concomitant with the death of personal responsibility. Not trying to flame here folks, just an opinion formed from a life lived on Unix/Linux/Irix/BSD/OSX systems and never having had to remove a virus even once. Am I alone in thinking that Microsoft is responsible for those viruses more than the virus writers are? The fact that I unwillingly support MCSE's who make virus removal a full-time job on my tax dollar while unix talent goes neglected and left useless to novel corporate agendas has nothing to do with this bitterness. Nope. It's Microsoft's own incompetence that deserves the bounty.
....that's always good advice.
Get your screenshots here.
Not sure about you but the first thing I thought of when reading this headline was that it applies to the RedHerring's mode(s) of commucation as well. phphhhhht! What was that? Smells like a money-grubbing silicon valley "journalist"-come-lately to me.
Although the post by Emmanual Dreyfus indicates that XDarwin is essentially a test case, this is a rather important test case. If you can run XDarwin, you're just a short hop away from having all of the X11 apps along with it. Also, imagine a package system like the fink working equally well on OSX and NetBSD. You could develop on OSX with its comfortable GUI and deploy to NetBSD with its comfortable price.
Really? Microsoft has done this for years.
They're still doing so. Longhorn anyone?
Two observations:
1. Even the N.Y. times wasn't able to offer much real evidence for merger talks. Also, remember that they are just talks, and a preference for IPO was stated by the company.
2. If Microsoft acquires Google, give them enough time and they will commercialize it to the point that it isn't as useful. At that point, the private world will once again rise up to meet the demand.
The real underlying conflict here is between privately and publicly owned business. The mass markets and finely tuned product quality have always been at odds.
BlueFish has occupied this space for quite some time. The spin is vintage Michael Roberson of course. We've been here before, people. He's an early adopter with a megaphone that's twice the size of yours. After all, HE KNEW ABOUT MP3 BEFORE YOU DID.
There are times I'd really wish that the tech media would genuinely research the subject matter instead of just amplifying hype. Hard-working, often-silent open source incumbent projects deserve nothing less.
Is it just me or is that Aqua-style X slashdot story icon looking outdated? What's needed is a metallic-style Panther X icon. Does Slashdot have a graphics-submission procedure? The XIcons site has a few that should work.
Here's a plausible scenario: Mr. RemainNameless stumbles across a major sql injection vulnerability while browsing a WidgetCompany's site. He realizes that WidgetCompany now has his originating IP# and ISP information in their web server log files and could track him down to accuse him of an attack on their server. What to do? If he comes forward, they can accuse of him of an attack. If he remains silent, the problem isn't fixed, and he might (especially if he is a security professional) be in trouble for not alerting anyone about this vulnerability, and there is record in the log files that he knew about it.
What's the best way to go about disclosing to a company that their network presence is vulnerable? What are the legal ramifications of doing so?
There's this little aluminum products manufacturing facility in rural Nebraska that makes great stuff for data centers, and the cost will pleasantly suprise you: www.mtpartners.com
Also, put the cables under your tiled floor, not in overhead racks. Typical overhead racks are open-air and human-accessible in a way in which tiled-in areas are not.
Finally, have someone skilled in the arts of physical security take a look at your building, entrance, etc. For example, I've seen people build really nice data centers about ten feet away from a busy road. They are unwittingly about one violent car wreck away from having their whole enterprise go down. Sure, there are concrete barriers for that sort of thing, but in both software and hardware, the best security is built in, and planned for from the beginning.
The STEAL lab at the Nebraska University Consortium of Information Assurance has a pretty nice setup that sounds similar to what the AskSlashdot post described. One thing I noticed when walking by the lab: they have signs up indicating that if you walk in through their door with a USB keydrive or a CDR, you can plan on walking out without it. The basic idea is that no electronic media, whatsoever, is allowed in or out without a CAREFUL audit of what's going on. If you're going to play with live viruses, the setup demands nothing less, I suppose. Remember that if you don't have physical security, network security doesn't make any difference.
The GIMP has a pretty robust featureset and you can download it for Linux or buy it for Win32 or the Mac.
There is also a rudimentary plugin now which handles CMYK color separations here. Also, the MacGIMP site had a story on the SVG changes as well before it was posted on Slashdot.
I have a unicode converter that works really well. It will put your email address into a form like:
...
& # 105;& # 032;& # 100;& # 111;& # 032;& # 105;& # 116;& # 032;& # 116;& # 104;& # 105;& # 115;& # 032;& # 119;& # 097;& # 121;
For the past three years or so, the spammers haven't caught on to this, and they are unlikely to do so given the few people who take the effort to put this measure into place.
P.S. It's not just mailto links that are being harvested here. They'll scrape anything with an @ or a "at" or
If you're running a mail server with, say, 250 people doing what you're doing, the spam connections might very well denial-of-service your mail server, assuming it is running on a typical T1. The expense of bandwidth, not to mention the inconvenience of less-reliable mail, is what leads sysadmins and the companies who employ them to take email obfuscation seriously.
There are people in the public relations world who drool over the possibility of having the world sit around and chat about your logo redesign. This is news for nerds. Apple has had their ten minutes of fame, now it is time for open source to shine. Would a redesigned Debian logo get coverage on slashdot? It shouldn't. The avoidance of mass-commercialism led me to slashdot and now it is driving me away.
I had a nice morse code response here, but the slashdot lameness filter won't let me post it. Talk about lame. "Reason: Please use fewer 'junk' characters." I'll readily admit that ASCII graffiti is junk, but morse code? C'mon! ;)
Yes, the difference between what verisign has started doing and what the domain name purveyors do is this: instead of just redirecting purchased domain names which have yet to be "pointed to" an IP#, they are redirecting any request for any domain name, in realtime that isn't already registered by use of a wildcard redirect, and furthermore, they are tracking the number of occurrances and origin of these requests with Overture web-bugs. This is a major privacy concern in addition to taking advantage of anyone who places trust in the the domain name architecture to look for a destination site.
1. The distributed network in its infancy is lovingly brought to life by researchers: arpanet is born.
...man in his time plays many parts, His acts being seven ages. At first the infant, Mewling and puking in the nurse's arms. And then the whining school-boy, with his satchel And shining morning face, creeping like snail Unwillingly to school. And then the lover, Sighing like furnace, with a woeful ballad Made to his mistress' eyebrow. Then a soldier, Full of strange oaths and bearded like the pard, Jealous in honour, sudden and quick in quarrel, Seeking the bubble reputation Even in the cannon's mouth. And then the justice, In fair round belly with good capon lined, With eyes severe and beard of formal cut, Full of wise saws and modern instances; And so he plays his part. The sixth age shifts Into the lean and slipper'd pantaloon, With spectacles on nose and pouch on side, His youthful hose, well saved, a world too wide For his shrunk shank; and his big manly voice, Turning again toward childish treble, pipes And whistles in his sound. Last scene of all, That ends this strange eventful history, Is second childishness and mere oblivion, Sans teeth, sans eyes, sans taste, sans everything.
2. Rapid protocol development as the network begins to start walking: from gopher to httpd to mosaic. Email and usenet populate most universities.
3. Private enterprise realize the potential and small companies start forming around services and products aimed at network usage. Network usage is a daily exercise for academics and early adopters. Linux arrives and Slashdot's squeaky pubescent voice first heard.
4. The internet meets the economy and Wall Street goes apeshit. Billion dollar companies are started, sustained, and identified by their position on the network and mindshare of net users. The network is the computer.
5. Infrastructure buildout is complete, and educated people worldwide use it as a communication medium. Initial high-growth opportunities are gone so Wall Street sours on the newness, returning its attention to fundamentals of profit-grubbing.
6. Annoying spammers take over, search engines are all manipulated, pop-ups for porn and travel are everywhere, Microsoft mass-marketed virus hysteria takes place, simple hosting efforts become a bitch.
7. Lawyers and short-sighted opportunists inexorably and slowly strip everything likeable from the network by lawmaking and lawsuits until there is nothing left but death and taxes.
Shakespeare's As You Like It (Act 2:7)
Dear Bob:
I was in Boston at the time and missed a chance to meet you at your talk at Brookhaven Lab in New York, a year or two before the Red Hat IPO. Now RedHat seems to be well on its way to be what Wall Street identifies with as a dominant Linux company. This took about four years to accomplish, which is pretty impressive in the grand scheme of things. A lot has changed since then. If you were now in your late twenties or early thirties and wanting to bootstrap a long-term business, what would you be work on?
ubiquitin
So now all of those wild-eyed grassroots Darwin users can rush out to download the source and compile. But seriously, in the rush to legitimize MacOSX to the GNU crowd, what happened to "stuff that matters"?
I can't speak for whoever is moderating my comments, but I from where I'm sitting this is not a blind hatred for Microsoft. It is absolutely a blind hatred for anyone wasting my tax dollars who shrugs off accountability.
Between procmail, spamassassin, bogofilter, mime defang, and any number of freely available solutions to the spam and virus epidemics, the *nix MTA problem set has a number of very effective low cost solutions ready to go. A sysadmin familiar with any scripting language (perl,bash,csh,etc) can script the patches to fix an arbitrary number of remote servers in short order. And do it securely!
I've recently heard a number of Windows/Exchange admins from different companies complaining about having to go from desk to desk, from seat to seat, from box to box applying patches which can't be scripted.
The thing about all those openssh patches is that I can control the patching mechanism itself in ways that MCSE's could only dream about. I desperately want the U.S. government to have full advantage of this efficiency instead of purchasing Symantec virus subscriptions at top dollar and then billing me next tax season for the self-congratulated job well done.
Your point about competent administration is well taken. Hopefully my point about technology tax dollars accountability will be too.