How can I 99% certain that my software is safe?

Question

0.00/5 (No votes)

See more:

Hi,

I have recently been creating a small application for a company I am working for. After a month of development, I was ready for testing. However the big IT "boss" has now put a hold on the project as the company does not allow "non-supported" software to be installed onto the works network.

They are also concerned that .NET 4 Framework will expose holes in there security.

The application itself does not connect to the internet and does not store data in anyway shape or form. This to me would seem like that although I have not specifically looked at the security side of things the application would not realy need a security system as such.

I am stuck, my entire job role was to create this application to speed up the work of a particular department now I am being told no due to security issues. Its extremly frustrating and I would appreciate any of your opinions on the matter.

Thanks

Dan

Posted 18-Jul-11 21:40pm

DanHodgson88

Add a Solution

2 solutions

Solution 1

please explain: what is "non-supported" software?

are you employee of this company or a contractor? in both cases f***** (=forget) the company and search a new job (silent search mode: search a new job FIRST an then leave).

Posted 18-Jul-11 21:44pm

Thomas Krojer

Updated 18-Jul-11 21:46pm

v4

Comments

DanHodgson88 19-Jul-11 3:48am

basically as far as I can gather, they are concerned when/if I left the company no one other than me could maintain the software if need be. The chap I spoke to told me they only buy software in yet they have hired me as an in house developer :s. It's going to be a long day!

I am an employee. Cheers that might well be the case of the matter absolute joke!

Sergey Alexandrovich Kryukov 20-Jul-11 2:14am

Good reply, my 5. Sometimes we waste time, but I call working for some companies "wasting my life". Maybe, this is the case. Maybe not though; it takes a great deal of patience, decency and bravery to convince illiterate people (like the "boss") to do right thing and this is not always hopeless. Judgement here is very difficult, but not wasting one's life is very important.
--SA

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Doc Lobster · Accepted Answer · 2011-07-18T22:25:00

Hi Dan,

I take from your user name that you are ~23. At that point of career I would think that its the job of your boss to tell you exactly what language, libraries and tools to use, what you should be aware of, etc. You should expect to have at least something like a requirement specification at hands.

If you don't get a precise assignment you can still ask questions e.g. "Is it okay for you if I use this and that?". Do not start coding as long as these "architecture"-decisions are unclear.

Also I would advise to accept "boss" decisions even if you do not agree with them. If you do not agree with them at all, tell your boss about your concerns. Prepare very well for that and stay focused on the topic.

If your boss does not change his opinion, solve the task as assigned. Do not alter decisions behind his back. If you do that, it won't matter any more if your solution is good or bad - it will be about him showing you who is boss.

Whatever happened, don't worry too much about it. There have been greater losses than a month's work. At least you have got paid for it (I hope). Maybe the project can still be salvaged.