|
Did you register the DLL in your system?
I must get a clever new signature for 2011.
|
|
|
|
|
yes i did...
now i have another error... "ERROR GrabFrame()
//Jpeg compression quality
short nQuality = 45;
//Shout a picture from my webcam
CAMSERVERLib.Camera cam = new CAMSERVERLib.CameraClass();
byte[] picture = (byte[])cam.GrabFrame(nQuality); ---> "ERROR GrabFrame().
//Add the hour to the jpeg picture
MemoryStream ms = new MemoryStream( picture );
Bitmap bmp = new Bitmap( ms );
xxx
|
|
|
|
|
The_Collector wrote: now i have another error... "ERROR GrabFrame()
What error?
I must get a clever new signature for 2011.
|
|
|
|
|
the words in BOLD is d ERRROR... "ERROR GrabFrame()"
xxx
|
|
|
|
|
the words in BOLD is d ERRROR... "ERROR GrabFrame()"
xxx
|
|
|
|
|
Well that makes it so much clearer.
I must get a clever new signature for 2011.
|
|
|
|
|
i dont understand...
but anyway, thanks for your effort....
just want to have a clearer answer on this things...
xxx
|
|
|
|
|
The_Collector wrote: i dont understand...
Nor do I, all you have said is "the words in BOLD is d ERRROR... "ERROR GrabFrame()"", which tells us nothing. What error, what messages, what status codes, what exceptions, etc? People reading this cannot guess what happens on your system.
I must get a clever new signature for 2011.
|
|
|
|
|
its a camserver.dll which doesn't give any error numbers or description, just this error....
xxx
|
|
|
|
|
So how exactly do you think anyone can guess what the problem is? I suggest you go to the site or supplier of the DLL and ask them for more information.
I must get a clever new signature for 2011.
|
|
|
|
|
i guess so... i'l try to reach d programmer of this dll or look for another dll..
thanks.
xxx
|
|
|
|
|
In addition tp pravin answer I also suggest you to go there[^] to download a sample application to learn how to capture image using webcam.
|
|
|
|
|
this is a windows application,,, Im looking for ASPX page.
thank you
xxx
|
|
|
|
|
Simple .NET licensing mechanism - how to crack this (assuming exe is obfuscated?)
<br />
class Program<br />
{<br />
static void Main(string[] args)<br />
{<br />
string EncryptedLicense = System.IO.File.ReadAllText("License.txt");<br />
if (LicenseManager.Decrypt(EncryptedLicense))
{<br />
Console.WriteLine("Valid license");<br />
}<br />
else<br />
{<br />
Console.WriteLine("Invalid license");<br />
}<br />
...<br />
}<br />
}<br />
dev
modified on Thursday, March 10, 2011 10:21 PM
|
|
|
|
|
Make a copy of License.txt?
--edit--
A link to the previous[^] thread would have helped. As is now, it looks like you're trying to breach someone else's protection.
I are Troll
|
|
|
|
|
lets assume license file is encrypted + contains machine IP address or MAC code with expiration date.
But where'd you store the private decryption key?
dev
|
|
|
|
|
By paying for a license. License mechanisms exist for a reason.
|
|
|
|
|
He's building one, and looking how people would attack it. Ie, is this lock enough on his door to keep the bad guys out? (A typical bad guy would be the average IT-manager who notes that you can re-download the evaluation-version, or to use the key from employee A to install the same product on the PC's of employees B and C)
I are Troll
|
|
|
|
|
There's a serious side to my answer. Suppose I tell him how to crack the application - then I have posted an answer in a forum that is crawled by various web crawlers; at this stage I have told just about any script kiddy out there how to do it as well. Now, this is a simplistic application, but the technique that applies will be similar.
|
|
|
|
|
Pete O'Hanlon wrote: <layer>Suppose I tell him how to crack the application - then I have posted an answer in a forum that is crawled by various web crawlers;
..right
A script kid would merely download a crack, not create one - by your reasoning, we'd be helping hackers simply by reporting leaks in Windows. After all, they are holes in existing systems, and Google would index them
I'm a firm believer that any hole should be pointed out, so that it can be closed.
I are Troll
|
|
|
|
|
That's right, so the only way to be secure and safe is never ever discuss security implications.
|
|
|
|
|
I'm considering buying third party + on top build one myself so two layers.
dev
|
|
|
|
|
Yes but how's that going to solve your problem? If their implementation is on .NET layer... then we might as well code it yourself right?
If on the other hand they patch the binary, I've reviewed one vendor's solution, you'd still end up need to write .NET level permissioning statements such as:
<br />
bool IsAuthorized = ThirdPartyLicensControl("ModuleName");<br />
if(IsAuthorized)<br />
{<br />
Module.IsEnabled = true;<br />
}<br />
dev
|
|
|
|
|
For native executables, placing NOP's in the appropriate locations does the trick. I did this to mine when investigating how hard/easy it would be for them to bypass my licensing mechanism. Now granted, I knew where to look in the executable but it ended up working so I'd say, your wasting your time. I gave up with licensing schemes but still choose to obfuscate as much as is practical.
[modified]
Geez, whoever one voted my comment has obviously never applied the machine instruction 90h (as many times as needed) to an native binary exectuable to manipulate branch statement execution. You might want to look it up in the intel handbooks under "instruction sets" and maybe try manipulating the execution paths in the executable. I think you'll learn a thing or two. Also you might want to read a security book or two about why you shouldn't put any faith in hiding secrets in your code.
Granted the OP was talking about managed code but the concepts are basically the same.
modified on Friday, March 11, 2011 12:20 PM
|
|
|
|
|
yes I hear you (though I dont know assembly programming)
Binary patch is the bottom line - if hacker knows where the code is which makes the comparison
<br />
IsAuthorized = LicenseController.CheckPermission("ModuleName");<br />
if(IsAuthorized)<br />
{<br />
... load the module ..<br />
}<br />
The question is, how hard/easy to spot the line? If code is obfuscated (In machine code it'd be same cmp command but there're still thousands of them hacker would need to try patching them one by one, right? This leads me to thinking dynamically generate millions of comparison operators [which is never on actual runtime execution path of course] in .NET code to further throw the sucker off the trail)
Another question is where to store decryption key?
dev
modified on Saturday, March 12, 2011 7:58 PM
|
|
|
|