|
"Encrypted" passwords are only marginally better than passwords stored in plain-text.
Passwords need to be stored using a salted one-way hash, with a unique salt per record. Read the articles I linked to in my previous reply for details.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
kerek2 wrote: and got this Error :
ORA-06550: line 1, column 7:
PLS-00801: internal error [22503]
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
Did you read something about these ORA-06550 and other errors?
Like [Oracle / PLSQL: ORA-06550 Error Message](https://www.techonthenet.com/oracle/errors/ora06550.php)
|
|
|
|
|
Yup already read it, for info...my password in Db is encrpted, so i try to use stored procedure to check whether the username n password is correct or not and will return the value 0 or 1,
Blank to do it, plz guide me sir, tq
|
|
|
|
|
In your Stored Procedure you are attempting to use the type (%TYPE) cms_user.cu_username but you haven't supplied the definition for that type.
In your VB code you are trying to pass username as a VarChar
Try changing your stored procedure to be
function validateUser(username in varchar2,.. and see if that has any effect.
|
|
|
|
|
Hello 
I have the problem of packing multiple XML files with TAR format.
I am using the language Visual Basic 6, with which I create from one to less than 500 XML files, to later want to pack them with the TAR format, generating a file called package.tar, which in turn I will have to compress with GZIP to finally build a file called package.tar.gz
I tried the code of this website https://github.com/wqweto/VszLib, but I can only create files called package.7z
Does anyone have any idea how to solve my problem? 
Excuse me for my writing, it is that I do not speak english, and I translated this message with googletranslate from spanish.
Bye
|
|
|
|
|
Nobody uses VB6 any more. It's been obsolete for over 20 years.
You're going to have to write that code yourself if there are no prewritten libraries. You can Google for "tar vb6" and start looking at the results.
|
|
|
|
|
Use an external program; there's some command-line executables that create tars', and VB6 can easily execute those.
..but if it is an important application, you better start upgrading.
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
How to get the encoding of libre-office from the VBA code ?
For example encoding can be UTF-8,UTF-16,etc.How to retrieve this from vba code?
If anybody has any idea provide help.
Thanks.
|
|
|
|
|
It sounds like you're assuming that every file has an encoding. This is not the case.
There MIGHT be a byte order mark in the first 2 to 4 bytes of the file. Those bytes will tell you what the encoding is. See Byte order mark - Wikipedia[^] for what those bytes are.
If the byte order mark is not there, there is no reliable way of determining what the encoding is, if any. Usually, if there is no byte order mark, you assume it's ASCII or UTF-8.
|
|
|
|
|
A crude way is to apply an encoding and run a spell-checker. The one with the least spelling-errors is probably the encoding used.
Not very efficient and not bullet proof.
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Hi to everyone,
in my program i compare 2 byte array to check haw many byte are the same(true value only).
For this scope i use a for next that compare any position of Arr1 with Arr2
I thing that exist a more efficent way to do this.
An example
arr1 = 0011 0000 1011
Arr2 = 0100 1100 1010
return me 2 because position 9 and 11 are 1
Any idea?
Tnx
Salvo
|
|
|
|
|
Do you compare BYTE or bit arrays?
How are you doing the compare? Could you show your code?
|
|
|
|
|
You could (maybe) use a logical AND operation on each pair of bytes, and count the non-zero bytes (or bits) in the result. for example in your data above:
arr1 = 0011 0000 1011
Arr2 = 0100 1100 1010
==== ==== ====
0000 0000 1010 - the result of the AND operation
|
|
|
|
|
Good morning to the whole community, ![Java | [Coffee]](https://www.codeproject.com/script/Forums/Images/coffee.gif)
I would like to expose a problem, I hope you can help me.
I have a fully functional exe on the machine where it was developed, but malfunctioning with Debug JIT message series on normal W10 64 clients with latest updates. Going to check the .Net Framework versions installed on the clients, I find 4.8. Trying to install the .Net Framework version with which I developed the software but runtime version, the .Net Framework installer tells me that it is not possible to continue as there is already a more recent version. Now I wonder what should I do? Do I need to install the Developer version? I don't understand why it works perfectly on the machine where it was developed while on other clients it doesn't. .Net Framework: 4.6.1 Code: VB.NET
thank you so much and I hope you can help me 
Google translate
|
|
|
|
|
Before you do anything, you need to investigate the problem to find out what is going wrong. If you change something on the target machine you could make the problem worse.
|
|
|
|
|
On the target machine I have not changed anything except the attempt to install the net framework runtime 4.6.1. How fair it is of course. But since there is 4.8 on the client, the setup stops saying that there is no point in installing 4.6.1. I don't understand, however, for what reason if the software works very well on the machine I develop, on other clients it gives errors. I was wondering if it was appropriate to install the NF 4.6.1 Developer Kit.
Thanks so much
Google translate
|
|
|
|
|
There is no point in trying to guess what the problem is. You need to find out exactly what is causing the failures. You cannot make changes to the system until you know exactly what the problem is. Also, the .NET frameworks are forward compatible (mostly), so an application built on 4.6.1 should run on 4.8.
|
|
|
|
|
No, there's no point.
Installing 4.8 includes everything .NET 4.x to that point, including 4.6.1.
This is something wrong in your code or some assumption you made when writing it.
|
|
|
|
|
eusta wrote: I would like to expose a problem, I hope you can help me.
I have a fully functional exe on the machine where it was developed, but malfunctioning with Debug JIT message series on normal W10 64 clients with latest updates. Going to check the .Net Framework versions installed on the clients, I find 4.8.
What is the exception logged? "FileNotFound"?
Bastard Programmer from Hell
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
I solved. Fault of one of the hundreds of obfuscators that NEVER work !!
|
|
|
|
|
The fact that you've run your application through an obfuscator before trying to run it is probably something you should have mentioned previously.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I could tell you that you are right, but the point is this: why shouldn't I trust an obfuscator especially those with paid license?
The obfuscators issue is a real dilemma. I've tried dozens of them, free and licensed, but none and again none have ever worked 100%. I thought I had found one for a fee but with the possibility of testing it. This is what it produced: A software that only works as a facade, but when it comes to handling large amounts of code, libraries and functions in general, IT SHALL FAILED! Gentlemen let's face it: obfuscators for .NET don't work. Or at least they don't work for large amounts of code to manage. End.
Thanks a lot to everyone.
|
|
|
|
|
Or you run the obfuscators on the assemblies that they don't break and don't run it on assemblies that do, like ones the use Reflection.
|
|
|
|
|
I did not understand what you are suggesting to me
|
|
|
|
|
You don't run the obfuscator on every .exe and .dll (assemblies) in your app. You only run it on the assemblies you want to protect, but only if those assemblies can even have the obfuscator run on them. If not, you have to consider moving the code that's making the obfuscated version fail to another assembly.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
