when you get to college, you'll feel like high-school girls are annoying little kiddies, even if they are cute. your friends will laugh at you for going to the high-school prom & you'll feel like a wanker. plus, you'll have all these hot college chicks your own age to drool over.
after you get a job, the college girls will still be hot. your friends will cheer you on for scoring a young chick, but you'll be embarrassed that she can't meet you for a drink at the pub. she'll flake out on you after two months. two or three of these and you'll eventually decide that you need someone a little more stable. plus, you'll have all these hot office cuties to drool over.
after you get married, all other women are off-limits so it doesn't really matter. if a young chick flirts with you then you'll feel like a total stud and that you've still got "it." you won't have the time, energy or inclination to do anything about it. but, you'll brag to your friends that the young chicks still dig you.
basically, don't worry about it. there will be plenty of hot chicks your own age every step of the way. you'll just natually move on.
I like the idea, but speeding up my development by 10x I don't think is realistic. Perhaps if i had to start from scratch and make a table editing page. But, no developer who is working full time starts from scratch. I have a bag of tricks just like everybody else. Using datagrids, components, personal code libs, code generators, etc, i can have a basic UI for all tables in a database in a few seconds in any language i want. the harder, more time-consuming part is combining all of it into a usable application. sometimes the framework can help with a simple structure, but becomes a burden with complicated relationships and things that don't directly map to the table fields.
Its the same problem with ORM solutions. the easy stuff is easier, but the harder stuff can be even harder.
this reminds me of the dotcom companies in the heyday that spent all of their venture capital on a superbowl ad and then went out of business six months later.
I know this is petty, but.. almost all distro screenshots look really fantastic with one exception. That craptastic clock with the fake digital font looks so terrible. i can't stand it! It seems really outdated, yet all the distro screenshots have that same terrible font. Hasn't anybody changed that?
I just built a PVR, so I can appreciate the challenge of making it quiet. You don't really realize how loud your PC is until you actually put it in your living room full-time.
I have to say that making the thing quiet turned out to be the most expensive part of the project. You have to get special versions of everything - special power supply, special cpu fan, special hard drive (laptop drive w/ adapapter in my case).
I finally have it pretty quiet, but the DVD drive is the final kicker for me. I can't seem to find a quiet *black* dvd drive and these things are noisy as hell! luckily, it only makes noise while its playing a movie, so the volume is usually up.
I love the idea, but I have a feeling it can backfire, though. The spammer controls the DNS, so Lycos is basically giving them a third-party DOS hose to turn on whoever they like. Yes, if they do that then people cannot get to their product. But, as soon as they see their traffic spike, they point the hose at someone else. Then the lawsuits will start to appear.
If staff at lycos are actually real-time monitoring this to make sure that the right person is getting shafted, then it could work.
That being said, sign me up! Whatever makes the spammers job harder & more expensive is ok by me.
Not to defend Microsoft, but they probably just outsourced these audio files from an audio production house. (And, likely, they paid a nice sum of money for the work and rights to use the audio). Sound Forge is a mastering program, so it might have gotten the tag added later down the chain by yet another production house.
I wouldn't be surprised if many of our companies have outsourced some work (graphics for the website, etc) and the actual work was done by an artist that was using a cracked version of photoshop or whatever. Hell, I might have hired a plumer to work on my house who was using stolen tools. I wouldn't accept any responsibility for that and it certainly doesn't mean that I condone stealing tools. I would be a different story if I knew about or encouraged the use of stolen tools.
Unless you have machines on your network running 95/98 you should disable LM Hash in Windows. It is there only for backwards compatibility and you can disable it easily:
The argument concering that he "had the skills necessary" to create the virus aren't really that convincing to me.
The comparible code-base (unusual string concatanations that appear in both the virus and his commercial software) I suppose I *could* also overlook that because I know that a lot of developers copy code snippets from support pages and such. Especially for such generic functions as sending email.
But, then throw in the fact that send-safe and the sobog virus have very consistent release schedules. That is a little suspicious.
Not only that, but, if you remember when SoBig first came out - it was quite a long time after before people started to realize that it was creating spam proxies. send-safe was using those proxies even before the massive outbreak. Now that is kinda weird.
So, when you add up all of those things, It seems convincing to me. Is it enough to raid his office computers?
It seems like most Windows virus writers just adapt someone elses "proof of concept" virus, or take a virus that's already written and add their own payload. I've been wondering when someone would get some wide-spread attention with a Linux virus. All of the copy-cats will probably take this code and, thanks to the helpful suggestions here on slashdot, fix the bugs and do a better job with the phishing email. I have a feeling we haven't seen the last of this..?
The difference is that your system was built to sound good. The dudes that cruise by my place could care less about good sound. They build their system specifically to be loud on the outside. It's a macho thing.
Windows browsers (including IE) run as the current user. However, most people are running their Windows machine with admin permissions. So, if the current user is compromised, the machine is basically owned.
*nix users would be safer because most people don't run their desktop as root.
It might be valid to compare modded computers with, say, fancy tire rims. But, the souped-up audio systems impose themselves on everyone - even if you are nowhere near the car. Additionally, for some reason, it ususally seems to occur mostly at 2am.
Not only that, but, as awesome as the music may sound inside the car, those of us on the outside only hear low-frequency rumble combined with the sound of the car frame shaking. I'm a musician and I love good, loud music. When I want to hear it, I go to a club or crank the stereo in my own home. But, waking up in the middle of the night to the sound of a car stereo system overloaded and distorted is just annoying.
It's basically just an easy way for a muscle-neck jackass to proclaim "look how rude and annoying I am!" It's a power-trip because they have the ability to go around and create a big scene.
I think that I understand what you mean, however your terminology is perhaps a little confusing. When a program *crashes* I tend to think that it has hit an unhandled exception. I think you are actually trying to say "handle the error and terminate." That is a very different thing from *crash* in my mind.
That being said, I disagree with your point that an app should always terminiate when it hits some bad input. My opinion is that the program should terminate if, by continuing, it will be forced into an unknown state. Streaming audio/video apps are examples of software built to keep going if they get bad data. If some packets get lost and/or corrupt packets get through, it might skip, show static, play a little distortion, etc. But, it won't just terminate. If a video player terminated whenever it got a bad packet, it would probably be worthless.
Just because IE (or any browser) gets some malformed HTML code doesn't necessarily mean that it is going into an unknown state. If the browser app realizes that it has malformed HTML, then it is still in full control and can choose to render as much or as little as it can.
Outsources has been about the best thing that corporate management could have hoped for. During the Internet boom, techies had upper management by the balls. Now they only have to mention the word outsourcing and all the techies go scurrying back to their cubicles in fear.
Fear is a tactic used by corporations to keep employees in line and working for low wages. Don't let all the hype get you down. Be smart and make yourself useful at your company. Companies need smart people. Outsourcing is not going to change that.
Re:Found the original program
on
Netscape Turns 10
·
· Score: 2, Interesting
I just tried it. Ah, the memories. I remember downloading this along with trumpet winsock - it was like a new world!
I just gave it a quick trial and here's some interesting results:
slashdot.org - doesn't work (promps for a file download)
netscape.com - loads, then immediately crashes the browser
Hibernate is probably not the type of thing that you would know about unless you are doing larger enterprise development in Java. You can use it for simple apps, but it probably just adds a bunch of unecessary bulk and complexity. If you're working on a large system, it can do a lot of the boring, tedious work for you.
I was fortunate enough to work with a client that dedicated one of our developers to researching Hibernate. He gave us a little presentation with his findings.
Basically, if you find yourself writing object wrappers around your database objects, then Hibernate will potentially save you some time. You don't have to think about the mundane details of mapping fields. Hibernate lets you define everything in configuration files and then it takes care of the data access functions. You can tell it about your primary keys, foreign keys, constraints, etc. It will enforce everything. If you do it right, you don't have to write SQL code to interact with the database. It's all done under the hood.
In keeping with the name hibernate, it also persists objects in memory and grab them from the database "automagically" as needed. So, that gives you some level of caching without your having to think about it. When you get a new instance of, say, customer object #1, Hibernate may populate it from the database. Or, it may grab it from memory. You don't need to know. It is smart enough to deal with transactions as well, although I haven't looked very deeply in to that aspect. It handles just about every other annoying situation you can imagine having to do with the plumbing.
Like a lot of developers, I'm protective about handing off important control over my app to a third party component (or set of components). If you are not comfortable, Hibernate is probably not for you.
The verdict of our team is that we will be implementing Hibernate in our next major development effort. So, I will be deep in it soon!
Once I was riding my bike to high-school and some jerk dumped their coke on me as they drove by. True Story. Had I been riding an e-bike, I might have been electrocuted.
More like the OS is as secure as the admin maintaining it.
I think it's a dangerous attitude to believe that you're secure just because you run Linux. 50 unpatched exploits on a Windows box vs 1 unpatched exploit on a Linux box - you're owned either way. Unless you're keeping a close eye on things, your *nix box could get owned and you wouldn't even think to notice.
I wonder if MS has a secret department dedicated to writing worms for Linux boxes? It seems like it would be a huge publicity boost for Windows if a significant worm or virus broke that affected only *nix boxes.
Linux, Macs and all other OSs are enjoying some degree of protection simply because Windows is a bigger, possibly easier target. But almost any system can be hacked. The attitude that Linux is 100% secure is likely to catch a lot of people with their pants down one of these days.
Slashdot Mirror
when you get to college, you'll feel like high-school girls are annoying little kiddies, even if they are cute. your friends will laugh at you for going to the high-school prom & you'll feel like a wanker. plus, you'll have all these hot college chicks your own age to drool over.
after you get a job, the college girls will still be hot. your friends will cheer you on for scoring a young chick, but you'll be embarrassed that she can't meet you for a drink at the pub. she'll flake out on you after two months. two or three of these and you'll eventually decide that you need someone a little more stable. plus, you'll have all these hot office cuties to drool over.
after you get married, all other women are off-limits so it doesn't really matter. if a young chick flirts with you then you'll feel like a total stud and that you've still got "it." you won't have the time, energy or inclination to do anything about it. but, you'll brag to your friends that the young chicks still dig you.
basically, don't worry about it. there will be plenty of hot chicks your own age every step of the way. you'll just natually move on.
exactly.
I like the idea, but speeding up my development by 10x I don't think is realistic. Perhaps if i had to start from scratch and make a table editing page. But, no developer who is working full time starts from scratch. I have a bag of tricks just like everybody else. Using datagrids, components, personal code libs, code generators, etc, i can have a basic UI for all tables in a database in a few seconds in any language i want. the harder, more time-consuming part is combining all of it into a usable application. sometimes the framework can help with a simple structure, but becomes a burden with complicated relationships and things that don't directly map to the table fields.
Its the same problem with ORM solutions. the easy stuff is easier, but the harder stuff can be even harder.
this reminds me of the dotcom companies in the heyday that spent all of their venture capital on a superbowl ad and then went out of business six months later.
I know this is petty, but.. almost all distro screenshots look really fantastic with one exception. That craptastic clock with the fake digital font looks so terrible. i can't stand it! It seems really outdated, yet all the distro screenshots have that same terrible font. Hasn't anybody changed that?
Myself and pretty much all of my IT friends all seem to play in one band or another.
Oh, wait.. you said *make money* on the side... forget it!
I just built a PVR, so I can appreciate the challenge of making it quiet. You don't really realize how loud your PC is until you actually put it in your living room full-time.
I have to say that making the thing quiet turned out to be the most expensive part of the project. You have to get special versions of everything - special power supply, special cpu fan, special hard drive (laptop drive w/ adapapter in my case).
I finally have it pretty quiet, but the DVD drive is the final kicker for me. I can't seem to find a quiet *black* dvd drive and these things are noisy as hell! luckily, it only makes noise while its playing a movie, so the volume is usually up.
I love the idea, but I have a feeling it can backfire, though. The spammer controls the DNS, so Lycos is basically giving them a third-party DOS hose to turn on whoever they like. Yes, if they do that then people cannot get to their product. But, as soon as they see their traffic spike, they point the hose at someone else. Then the lawsuits will start to appear.
If staff at lycos are actually real-time monitoring this to make sure that the right person is getting shafted, then it could work.
That being said, sign me up! Whatever makes the spammers job harder & more expensive is ok by me.
Not to defend Microsoft, but they probably just outsourced these audio files from an audio production house. (And, likely, they paid a nice sum of money for the work and rights to use the audio). Sound Forge is a mastering program, so it might have gotten the tag added later down the chain by yet another production house.
I wouldn't be surprised if many of our companies have outsourced some work (graphics for the website, etc) and the actual work was done by an artist that was using a cracked version of photoshop or whatever. Hell, I might have hired a plumer to work on my house who was using stolen tools. I wouldn't accept any responsibility for that and it certainly doesn't mean that I condone stealing tools. I would be a different story if I knew about or encouraged the use of stolen tools.
Even still, I find it amusing.
no bumper sticker, but here's a banner...
Unless you have machines on your network running 95/98 you should disable LM Hash in Windows. It is there only for backwards compatibility and you can disable it easily:
; EN-US;q299656
http://support.microsoft.com/default.aspx?scid=KB
The argument concering that he "had the skills necessary" to create the virus aren't really that convincing to me.
The comparible code-base (unusual string concatanations that appear in both the virus and his commercial software) I suppose I *could* also overlook that because I know that a lot of developers copy code snippets from support pages and such. Especially for such generic functions as sending email.
But, then throw in the fact that send-safe and the sobog virus have very consistent release schedules. That is a little suspicious.
Not only that, but, if you remember when SoBig first came out - it was quite a long time after before people started to realize that it was creating spam proxies. send-safe was using those proxies even before the massive outbreak. Now that is kinda weird.
So, when you add up all of those things, It seems convincing to me. Is it enough to raid his office computers?
The email subjects and message text in the screenshots are classic. Ah, how many of those have I filtered out?
It seems like most Windows virus writers just adapt someone elses "proof of concept" virus, or take a virus that's already written and add their own payload. I've been wondering when someone would get some wide-spread attention with a Linux virus. All of the copy-cats will probably take this code and, thanks to the helpful suggestions here on slashdot, fix the bugs and do a better job with the phishing email. I have a feeling we haven't seen the last of this..?
The difference is that your system was built to sound good. The dudes that cruise by my place could care less about good sound. They build their system specifically to be loud on the outside. It's a macho thing.
Windows browsers (including IE) run as the current user. However, most people are running their Windows machine with admin permissions. So, if the current user is compromised, the machine is basically owned.
*nix users would be safer because most people don't run their desktop as root.
It might be valid to compare modded computers with, say, fancy tire rims. But, the souped-up audio systems impose themselves on everyone - even if you are nowhere near the car. Additionally, for some reason, it ususally seems to occur mostly at 2am.
Not only that, but, as awesome as the music may sound inside the car, those of us on the outside only hear low-frequency rumble combined with the sound of the car frame shaking. I'm a musician and I love good, loud music. When I want to hear it, I go to a club or crank the stereo in my own home. But, waking up in the middle of the night to the sound of a car stereo system overloaded and distorted is just annoying.
It's basically just an easy way for a muscle-neck jackass to proclaim "look how rude and annoying I am!" It's a power-trip because they have the ability to go around and create a big scene.
I think that I understand what you mean, however your terminology is perhaps a little confusing. When a program *crashes* I tend to think that it has hit an unhandled exception. I think you are actually trying to say "handle the error and terminate." That is a very different thing from *crash* in my mind.
That being said, I disagree with your point that an app should always terminiate when it hits some bad input. My opinion is that the program should terminate if, by continuing, it will be forced into an unknown state. Streaming audio/video apps are examples of software built to keep going if they get bad data. If some packets get lost and/or corrupt packets get through, it might skip, show static, play a little distortion, etc. But, it won't just terminate. If a video player terminated whenever it got a bad packet, it would probably be worthless.
Just because IE (or any browser) gets some malformed HTML code doesn't necessarily mean that it is going into an unknown state. If the browser app realizes that it has malformed HTML, then it is still in full control and can choose to render as much or as little as it can.
Outsources has been about the best thing that corporate management could have hoped for. During the Internet boom, techies had upper management by the balls. Now they only have to mention the word outsourcing and all the techies go scurrying back to their cubicles in fear.
Fear is a tactic used by corporations to keep employees in line and working for low wages. Don't let all the hype get you down. Be smart and make yourself useful at your company. Companies need smart people. Outsourcing is not going to change that.
I just tried it. Ah, the memories. I remember downloading this along with trumpet winsock - it was like a new world!
I just gave it a quick trial and here's some interesting results:
slashdot.org - doesn't work (promps for a file download)
netscape.com - loads, then immediately crashes the browser
microsoft.com - loads fine, but looks plain !!
Hibernate is probably not the type of thing that you would know about unless you are doing larger enterprise development in Java. You can use it for simple apps, but it probably just adds a bunch of unecessary bulk and complexity. If you're working on a large system, it can do a lot of the boring, tedious work for you.
I was fortunate enough to work with a client that dedicated one of our developers to researching Hibernate. He gave us a little presentation with his findings.
Basically, if you find yourself writing object wrappers around your database objects, then Hibernate will potentially save you some time. You don't have to think about the mundane details of mapping fields. Hibernate lets you define everything in configuration files and then it takes care of the data access functions. You can tell it about your primary keys, foreign keys, constraints, etc. It will enforce everything. If you do it right, you don't have to write SQL code to interact with the database. It's all done under the hood.
In keeping with the name hibernate, it also persists objects in memory and grab them from the database "automagically" as needed. So, that gives you some level of caching without your having to think about it. When you get a new instance of, say, customer object #1, Hibernate may populate it from the database. Or, it may grab it from memory. You don't need to know. It is smart enough to deal with transactions as well, although I haven't looked very deeply in to that aspect. It handles just about every other annoying situation you can imagine having to do with the plumbing.
Like a lot of developers, I'm protective about handing off important control over my app to a third party component (or set of components). If you are not comfortable, Hibernate is probably not for you.
The verdict of our team is that we will be implementing Hibernate in our next major development effort. So, I will be deep in it soon!
Once I was riding my bike to high-school and some jerk dumped their coke on me as they drove by. True Story. Had I been riding an e-bike, I might have been electrocuted.
is it just me or does nyud.net rarely work?
either way, beware of that page - the images are really cool but after about 5 minutes i got a minor headache from looking at them.
More like the OS is as secure as the admin maintaining it.
I think it's a dangerous attitude to believe that you're secure just because you run Linux. 50 unpatched exploits on a Windows box vs 1 unpatched exploit on a Linux box - you're owned either way. Unless you're keeping a close eye on things, your *nix box could get owned and you wouldn't even think to notice.
I wonder if MS has a secret department dedicated to writing worms for Linux boxes? It seems like it would be a huge publicity boost for Windows if a significant worm or virus broke that affected only *nix boxes.
Linux, Macs and all other OSs are enjoying some degree of protection simply because Windows is a bigger, possibly easier target. But almost any system can be hacked. The attitude that Linux is 100% secure is likely to catch a lot of people with their pants down one of these days.