If they could make this work reliably it would be an excellent option for rural/remote areas who only have dial-up as an option. Even at that, their phone line quality is so poor that getting a connection can be difficult.
Satellite is an option for some but that typically involves satellite inbound traffic and dialup outbound traffic.
So, rather than positioning this as a product to compete against cable or dsl position it as a solution for areas where the electrical infrastructure exists but aren't yet reached by dsl or cable.
I think you'd have an interesting business plan. And take advantage of any government programs - the Canadian government, for example, will provide seed funding to organizations wishing to bring high speed internet access to rural or under-serviced areas.
Remember, Post-It-Notes (tm) are the result of a failed adhesive.
I don't think you can establish a set time frame for the general release of the information. You need to look at the severity of the vulnerability as well as the criticality of the system/application affected.
Further, one should also assess the impact of shutting down any affected service if a fix cannot be readily found.
To use the case in point... sendmail is critical to many firms that use it. Shutting down the service would be a drastic option. Implementing 'something else' would, typically, require a fair amount of effort. As such, you'd want to allow more time before releasing the information to the general public. But - it seems (and I haven't read the text of the exploit - but have upgraded my systems anyway) this is a remote root exploit which would tend to lessen the time allowed for announcing any vulnerabilities.
So, I don't think you can create a single standard but you might be able to create a standard for an application. Even that won't fit all cases but could serve as a 'rule of thumb'.
"What we did is a series of experiments in which we were trying to look at functional asymmetry in men and women of homosexual orientation, compared to a matched group of heterosexuals. And what we found was a two to one ratio. There was a very high incidence of people who were not consistently right handed among the gay people." - Exploring your brain
As the owner of a small programming firm I take the same attitude. Manage by objective. Deal with problem employees as exceptions and not the rule. And deal with problems swiftly - the other employees know when a co-worker is f*cking the dog and they resent it. After a while they'll begin to wonder why they're working so hard.
We carry this a little further... programming takes an enormous amount of concentration. If you have family problems then you aren't going to be much good to me. Go home and get them straightened out.
The result has been an extremely loyal, hard working group who will, without being asked, stay to complete the job no matter how long it takes. They are, of course, paid for that time and food is brought in when required... but they don't have to ask if they'll be compensated. They know they will.
The rules here are... don't do anything illegal and if you find some good porn - you have to share it.
Point well made. I've forgotten who said it but "light a candle, don't yell into the darkness" seems fitting.
Also, it seems to me that your proposed direction would align nicely with the strategies employed by companies such as Red Hat.
Good plan... let's give 'em the vote too.... can't get any worse. Can it?
... at a store near you.
In Openswan OE is on by default and you have to edit your config file to turn it off. Fortunately - it's easy to disable.
Made me feel very bad for making fun of artsies back in school - guess they get the last laugh.
So my wish would be go to Art school, then get a job putting body paint on lovely ladies... oh yea... ;-)
Satellite is an option for some but that typically involves satellite inbound traffic and dialup outbound traffic.
So, rather than positioning this as a product to compete against cable or dsl position it as a solution for areas where the electrical infrastructure exists but aren't yet reached by dsl or cable.
I think you'd have an interesting business plan. And take advantage of any government programs - the Canadian government, for example, will provide seed funding to organizations wishing to bring high speed internet access to rural or under-serviced areas.
Remember, Post-It-Notes (tm) are the result of a failed adhesive.
Further, one should also assess the impact of shutting down any affected service if a fix cannot be readily found.
To use the case in point... sendmail is critical to many firms that use it. Shutting down the service would be a drastic option. Implementing 'something else' would, typically, require a fair amount of effort. As such, you'd want to allow more time before releasing the information to the general public. But - it seems (and I haven't read the text of the exploit - but have upgraded my systems anyway) this is a remote root exploit which would tend to lessen the time allowed for announcing any vulnerabilities.
So, I don't think you can create a single standard but you might be able to create a standard for an application. Even that won't fit all cases but could serve as a 'rule of thumb'.
Regards...
Reference:
Mapping the mysteries of the mind
"What we did is a series of experiments in which we were trying to look at functional asymmetry in men and women of homosexual orientation, compared to a matched group of heterosexuals. And what we found was a two to one ratio. There was a very high incidence of people who were not consistently right handed among the gay people." - Exploring your brain
Offtopic = Yes
Intent = Funny
As the owner of a small programming firm I take the same attitude. Manage by objective. Deal with problem employees as exceptions and not the rule. And deal with problems swiftly - the other employees know when a co-worker is f*cking the dog and they resent it. After a while they'll begin to wonder why they're working so hard.
We carry this a little further... programming takes an enormous amount of concentration. If you have family problems then you aren't going to be much good to me. Go home and get them straightened out.
The result has been an extremely loyal, hard working group who will, without being asked, stay to complete the job no matter how long it takes. They are, of course, paid for that time and food is brought in when required... but they don't have to ask if they'll be compensated. They know they will.
The rules here are... don't do anything illegal and if you find some good porn - you have to share it.
Plane, car and train crashes occur with a much higher frequency than Shuttle accidents.
Not that I wish for this.... but... have a few hundred more Shuttle accidents and no one will notice those either.
Point well made. I've forgotten who said it but "light a candle, don't yell into the darkness" seems fitting. Also, it seems to me that your proposed direction would align nicely with the strategies employed by companies such as Red Hat.