|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] > Is knowledge of user ID's generally considered to be a > "vulnerability"? Sort of. When attempting to compromise a target machine, any knowledge of user accounts can often greatly reduce the time it takes to do it. The problem with this 'vulnerability' is that you need to actually be on the machine to use it, although it's not quite the chicken & egg situation that it first sounds like - it can help once you're on the system by making life easier to determine which user profile(s) you *should* hijack to give you more access rights. A bigger 'vulnerability' in the same vein is that the sign-on screen is quite happy to tell you too much information - it will tell you if the user profile does/doesn't exist (half the battle) and then it will tell you, once you have a valid user profile, whether you got the password right/wrong. Ignoring the fact that you can set the system to disable both the device & user profile after n invalid attempts, the sign-on screen still gives too much information, IMHO, it should just report "invalid sign-on" and not tell you anything else. --phil
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.