Re: Help! Stop the shift from unlocking database

From: RedStar (noway_at_hotmail.com)
Date: 09/22/04 

Date: Tue, 21 Sep 2004 22:06:06 -0400

ah..so you mean that shift code i just asked about up above ...can't be
stopped unless user level security is activated.

But my problem is ..this program will eventually be on lots of other
computer systems. I have found that such user-level protection breaks down
when you simply move the file to
another computer.

(or is it the case that the new menu/shift disable and user security
combined will keep program safe on other systems ...from being tampered
with?)

DOne alot of Access but i've never been concerned with security before.

So what do you have to do to make sure the application stays closed once its
distrubuted?

TIA :)
RS*

"Rick Brandt" <rickbrandt2@hotmail.com> wrote in message
news:2rbrolF18862bU1@uni-berlin.de...
> "RedStar" <noway@hotmail.com> wrote in message
> news:se6dnZxupNKfKc3cRVn-uA@golden.net...
> > I'm a bit confused by this...
> > i'm not using any shift modifier code
> > but have the DB invisible and the special keys off...
> > if i RIGHT-CLICK on the app and select open...
> > the app opens into the database window and all is exposed.
> > (normally running app..hides DB window and auto loads my form that
covers
> > everything else :)
>
> There is no menu option for disabling the shift key. Disabling "special
keys"
> in the start menu is a separate issue. You can execute code to disable
the
> "ByPassKey" which is what disables the use of the shift key. Either you
have
> executed this code in this particular file or you have not. If you have
then
> how long they hold the shift is irrelevant.
>
> In addition, if you haven't implemented User-Level Security, then any file
where
> you have disabled the Shift Key can have similar code run against it that
will
> re-enable it by anyone who knows how to do this. With User-Level Security
> implemented you can at least restrict who can run this code to members who
have
> administrative authority.
>
>
> --
> I don't check the Email account attached
> to this message. Send instead to...
> RBrandt at Hunter dot com
>
>
>

Relevant Pages

  • [UNIX] IBM eGatherer ActiveX Code Execution (PoC, Exploit)
    ... Get your security news from a reliable source. ... IBM eGatherer ActiveX Code Execution ... my $class = shift; ... sub Exploit ...
    (Securiteam)
  • Re: database open control
    ... If a database password, the shift key shouldn't matter. ... If you've applied user-level security (so that users have to provide both a ... If you've applied your own security, ...
    (microsoft.public.access.formscoding)
  • Re: Why 64bit Delphi compiler from Borland may be meaningless!
    ... contemporary key sizes, a shift from 32-bit to 64-bit might, in typical ... this would leave room for security ... parameter changes, more frequent full handshakes, etc. ...
    (borland.public.delphi.non-technical)
  • Re: best way to give user rights to unlock accounts
    ... ever touching a green screen via FTP or ODBC, etc. Security by ignorance is ... green screens to scan in inventory. ... I have been asked to give someone in the warehouse the ability to unlock ... I dont want to give a shift ...
    (comp.sys.ibm.as400.misc)
  • Re: Help! Stop the shift from unlocking database
    ... > but have the DB invisible and the special keys off... ... There is no menu option for disabling the shift key. ... With User-Level Security ...
    (microsoft.public.access.forms)