|
Did you not notice the word "if"? 
You'll not only need to make sure your bug database is the only application and database on the server; you'll also need to make sure that the SQL service account is locked down, and that the server isn't part of your domain. Otherwise, a breach of that server would compromise your entire network.
You'll also need to keep detailed audit logs to track any unauthorised changes to the system. Unless, of course, you don't care about that, in which case you might as well not bother with any authentication or authorization, and just give the users direct admin access to the server.
All of which you wouldn't need to worry about if the front-end application was written properly in the first place.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: You'll not only need to make sure your bug database is the only application ...
Err...No I would (and have done so) make sure that the bug database and the production boxes had absolutely no commonality.
And I would do that regardless of how trustworthy/stable I thought the bug database was.
Richard Deeming wrote: All of which you wouldn't need to worry about if the front-end application was written properly in the first place.
If there is no commonality at all then I don't need to worry about if the front-end application was written properly in the first place. Which was in fact my point from the beginning.
|
|
|
|
|
Quote: I'd generally try to avoid leaving any security vulnerability open to any target audience, no matter how unlikely they are to try to exploit it
Such as using the Internet 
|
|
|
|
|
|
|
|
|
|
So you want me to use that tool for you? :/
What actually does it do? -_-
Favourite line: Throw me to them wolves and close the gate up. I am afraid of what will happen to them wolves - Eminem
~! Firewall !~
|
|
|
|
|
Read its description for what it does. This page is for tools that people find useful. Use it if you need it.
|
|
|
|
|
Great tool! Thanks for the contribution!
What is does is to shorten your e-mails for instance you can set a certain paragraph to be inserted after a certain works for ex "salesprod" and as you writing the software will detect it and replace it.
It has an enormous number of customization features, you can filter certain programs to be intercepted and you can even customize with specific input (a box will appear asking for a piece of information that will end up in the replaced phrase).
Worth looking into!
|
|
|
|
|
A colleague of mine shared with the rest of us a very interesting link.
How to debug anything with Visual Studio and JetBrains
So no recompiling old dlls for pdb files? 
This software is free and I think to give it a try. It looks promising.
I hope that this thread's place is in the Insider.
If not please excuse me
[Thread moved - Ed]
Microsoft ... the only place where VARIANT_TRUE != true
modified 17-Jul-14 9:25am.
|
|
|
|
|
You used to be able to do this in Reflector ages ago, back when it was free (you probably still can but it isn't free anymore)
Nice to see this functionality in dotpeek now, which is free
Free
|
|
|
|
|
|
I am sorry. I will know the next time.
If its possible someone please move the thread there.
Microsoft ... the only place where VARIANT_TRUE != true
|
|
|
|
|
|
|
Hey guys,
Some time ago at the company I work for we noticed that all the bug/issue trackers out there were simply much too complex/bloated for our needs. So we implemented a small bug tracker with a clean design and the bare minimum of functionality.
Users are not required to log in, they just need to enter their name.
The tracker can handle multiple bug lists (for us each list represents a product)
Two bug states, unresolved and resolved, additionally bugs can be marked as important.
Thinking that others might have similar thoughts, we decided to write a small setup script for it, and open source it:
https://github.com/DukeW/Bugster
Hope it will help some of you 
|
|
|
|
|
|
|
|
I created jQuery TriggerTracker to help track down problems related to triggering and handling jQuery events.
It has turned into a project that has saved me and others on my team hundreds of hours in debugging. I recently made it available for everyone on github.
https://github.com/intervalia/triggerTracker
TriggerTracker is a tool for tracking jQuery events. It is a single JavaScript file that, when loaded, provides output to the browser's console related to jQuery event triggering and event handlers.
How to use triggerTracker:
Just load triggerTracker as soon as possible after loading jQuery.
<script src="jQuery-1.11.0.min.js"></script>
<script src="trigger-tracker.js"></script>
|
|
|
|
|
|
|
Am researching to write an SD card reader/writer for ARM and ran across this HxD Hex editor[^]. Put in an SD card in my card reader tell it to open it and it breaks the output down into disk sectors.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
