1stly, I know this is in the wrong thread. Didn't know where to put it. Could a MOD move it to a relevant thread please
Thank you.
Anyways. I have setup a web site, onlt a single page that displays "woof"
It's running on a 2000 server under IIS
the only problem is, if someone tries to use the site, whether they are on my LAN or in the US, they get asked for a username and password. I created a user, with cut down permissions, called "Muppet" and this allows people to see my web site after logging in.
I don't want all visitors to enter a username and password
How can I disable this???
Woka
Last edited by Wokawidget; May 27th, 2004 at 02:22 PM.
Anyways, the default user is IUSR_APPSERVER, but it doesn't work.
The user exists in my active directory, but I just keep getting the authentication box popping up If I change this to user Bagder and let IIS deal with te password then it works...
What account should I use for this?
What permissions should the account have?
Why doesn't the IISdefault account work?
Originally posted by Wokawidget Yea. JUST BEN PLYING WTH HAT. sILLY APS LOCK
Anyways, the default user is IUSR_APPSERVER, but it doesn't work.
The user exists in my active directory, but I just keep getting the authentication box popping up If I change this to user Bagder and let IIS deal with te password then it works...
What account should I use for this?
What permissions should the account have?
Why doesn't the IISdefault account work?
Woka
Relax a little.
Allow anon access...make sure file sharing is not set to "Simple Sharing". You can either ask for a user name / password or not. That's upto you to decide.
The anon access requires you to enter a username and password that will be used for this connection.
The default that IIS used was IUSR_APPSERVER, which according to Active Directory is the account setup for anan web connection.
But this still pops an authentication box up
If I change the user to Administrator, then it allows me to view my web page without any authentication.
Why doesn't the default user work?
Is it bad to use the admin acc. in this way?
The anon access requires you to enter a username and password that will be used for this connection.
The default that IIS used was IUSR_APPSERVER, which according to Active Directory is the account setup for anan web connection.
But this still pops an authentication box up
If I change the user to Administrator, then it allows me to view my web page without any authentication.
Why doesn't the default user work?
Is it bad to use the admin acc. in this way?
Woka
Why dont you just create a new anon account and use that?
The anon doesnt work on most pc's after some time, because the name of your PC can change. notice the name of the user is generally the name given to the PC.
Create a new user in the domain manager and give he / she the necessary right. Do not use admin accounts.
When using components, instead of 3 install options (full, minimal and custom) I would only like 2.
ooooo, and a problem I have just run into...
I used Visual Studio installer.
My AppID was: BadgerGrowl
When I add this into Inno using:
Code:
AppID=BadgerGrowl
It actuall installs it in the reg as BadgerGrowl_is1 and therefore doesn't remove the previous version and leaves 2 copies on the PC. Surely this is a bug in Inno?
When using components, instead of 3 install options (full, minimal and custom) I would only like 2.
ooooo, and a problem I have just run into...
I used Visual Studio installer.
My AppID was: BadgerGrowl
When I add this into Inno using:
Code:
AppID=BadgerGrowl
It actuall installs it in the reg as BadgerGrowl_is1 and therefore doesn't remove the previous version and leaves 2 copies on the PC. Surely this is a bug in Inno?
Woka
reg? as in registry...
You need to read help in INNO and no this isn't a bug. [Uninstall] sections in INNO do not delete registry dependencies, you can still get rid of them (just look at the help file for [Registry]).
If I install this again then it looks for FISH in the uninstall bit of the reg and uninstalls it before installing a new version.
The problem is that with VSI it placed the entry FISH as expected, but with Inno I tell it the AppID is FISH, but it actually uses FISH_is1 and therefore the previous version does not get uninstalled.
This is a HUGE ****ing problem, and is unacceptable
Looking at the registry using inno? eh? You have lost me...how do I get Inno to UNINSTALL the previous version?
This optional section defines any registry keys/values you would like Setup to create, modify, or delete on the user's system.
By default, registry keys and values created by Setup are not deleted at uninstall time. If you want the uninstaller to delete keys or values, you must include one of the uninsdelete* flags described below.
The following is an example of a [Registry] section.
[Registry]
Root: HKCU; Subkey: "Software\My Company"; Flags: uninsdeletekeyifempty
Root: HKCU; Subkey: "Software\My Company\My Program"; Flags: uninsdeletekey
Root: HKLM; Subkey: "Software\My Company"; Flags: uninsdeletekeyifempty
Root: HKLM; Subkey: "Software\My Company\My Program"; Flags: uninsdeletekey
Root: HKLM; Subkey: "Software\My Company\My Program"; ValueType: string; ValueName: "InstallPath"; ValueData: "{app}"
The following is a list of the supported parameters:
Root (Required)
Description:
The root key. This must be one of the following:
HKCR (HKEY_CLASSES_ROOT)
HKCU (HKEY_CURRENT_USER)
HKLM (HKEY_LOCAL_MACHINE)
HKU (HKEY_USERS)
HKCC (HKEY_CURRENT_CONFIG)
Example:
Root: HKCU
Subkey (Required)
Description:
The subkey name, which can include constants.
Example:
Subkey: "Software\My Company\My Program"
ValueType
Description:
The data type of the value. This must be one of the following:
none
string
expandsz
multisz
dword
binary
If none (the default setting) is specified, Setup will create the key but not a value. In this case the ValueName and ValueData parameters are ignored.
If string is specified, Setup will create a string (REG_SZ) value.
If expandsz is specified, Setup will create an expand-string (REG_EXPAND_SZ) value. This data type is primarily used on Windows NT/2000/XP, but is supported by Windows 95/98/Me.
If multisz is specified, Setup will create an multi-string (REG_MULTI_SZ) value.
If dword is specified, Setup will create an integer (REG_DWORD) value.
If binary is specified, Setup will create a binary (REG_BINARY) value.
Example:
ValueType: string
ValueName
Description:
The name of the value to create, which can include constants. If this is blank, it will write to the "Default" value. If the ValueType parameter is set to none, this parameter is ignored.
Example:
ValueName: "Version"
ValueData
Description:
The data for the value. If the ValueType parameter is string, expandsz, or multisz, this is a string that can include constants. If the data type is dword, this can be a decimal integer (e.g. "123"), a hexadecimal integer (e.g. "$7B"), or a constant which resolves to an integer. If the data type is binary, this is a sequence of hexadecimal bytes in the form: "00 ff 12 34". If the data type is none, this is ignored.
On a string, expandsz, or multisz type value, you may use a special constant called {olddata} in this parameter. {olddata} is replaced with the previous data of the registry value. The {olddata} constant can be useful if you need to append a string to an existing value, for example, {olddata};{app}. If the value does not exist or the existing value isn't a string type, the {olddata} constant is silently removed. {olddata} will also be silently removed if the value being created is a multisz type but the existing value is not a multi-string type (i.e. it's REG_SZ or REG_EXPAND_SZ), and vice versa.
On a multisz type value, you may use a special constant called {break} in this parameter to embed line breaks (nulls).
Example:
ValueData: "1.0"
Permissions
Description:
Specifies additional permissions to grant in the registry key's ACL (access control list). It is not recommended that you use this parameter if you aren't familiar with ACLs or why you would need to change them, because misusing it could negatively impact system security.
For this parameter to have an effect the user must be running Windows 2000 or later (NT 4.0 is not supported due to API bugs) and the current user must be able to change the permissions on the registry key. In the event these conditions are not met, no error message will be displayed, and the permissions will not be set.
This parameter should only be used on registry keys private to your application. Never change the ACLs on a top-level key like HKEY_LOCAL_MACHINE\SOFTWARE, otherwise you can open up security holes on your users' systems.
The specified permissions are set regardless of whether the registry key existed prior to installation. The permissions are not set if ValueType is none and the deletekey flag or deletevalue flag is used.
This parameter can include one or more space separated values in the format:
<user or group identifier>-<access type>
The following access types are supported for the [Registry] section:
full
Grants "Full Control" permission, which is the same as modify (see below), but additionally allows the specified user/group to take ownership of the registry key and change its permissions. Use sparingly; generally, modify is sufficient.
modify
Grants "Modify" permission, which allows the specified user/group to read, create, modify, and delete values and subkeys.
read
Grants "Read" permission, which allows the specified user/group to read values and subkeys.
Example:
Permissions: authusers-modify
Flags
Description:
This parameter is a set of extra options. Multiple options may be used by separating them by spaces. The following options are supported:
createvalueifdoesntexist
When this flag is specified, Setup will create the value only if a value of the same name doesn't already exist. This flag has no effect if the data type is none, or if you specify the deletevalue flag.
deletekey
When this flag is specified, Setup will first try deleting the entire key if it exists, including all values and subkeys in it. If ValueType is not none, it will then create a new key and value.
To prevent disasters, this flag is ignored during installation if Subkey is blank or contains only backslashes.
You can delete registry keys before installs..that is why I said [REGISTRY] in INNO
That's even worse
I don't want to delete the reg entry of the previous version. I want it uninstalled, as in if I did control panel, add/remove programs.
using your method what happens to the previous installations files?
Originally posted by Wokawidget That's even worse
I don't want to delete the reg entry of the previous version. I want it uninstalled, as in if I did control panel, add/remove programs.
using your method what happens to the previous installations files?
Woka
Woka either I am smoking crack or you are smoking crack or we both are smoking crack :-)
When you create an INNO script, you have a section for UNINSTALL and now one for REGISTRY. The uninstall and registry work hand in hand. Your application creates an uninstall icon right through INNO. So when you run it it also deletes the registry code. What the hell am I missing here
If I install with Inno then it's fine. previous versions get uninstalled.
If a previous version was packaged with anotehr installer then Inno installs a 2nd version of the App.
Inno knows what previous version to uninstall as the reg entry, as explained above, is the same as the currect install AppID.
but if I set the AppID to Badger (The ID that VSI uses and places in the reg) then Inno adds _is1 to it. Badger_is1 DOES NOT exist in my uninstall registry and therefore the previous version doesn't get uninstalled. I end up with 2 copies on my PC.
This will not uninstall all the apps components, like if I uninstalled it from control panel, it just removes the uninstall entry from the reg...or does this auto uninstall the previous version?
If I install with Inno then it's fine. previous versions get uninstalled.
If a previous version was packaged with anotehr installer then Inno installs a 2nd version of the App.
Inno knows what previous version to uninstall as the reg entry, as explained above, is the same as the currect install AppID.
but if I set the AppID to Badger (The ID that VSI uses and places in the reg) then Inno adds _is1 to it. Badger_is1 DOES NOT exist in my uninstall registry and therefore the previous version doesn't get uninstalled. I end up with 2 copies on my PC.
This will not uninstall all the apps components, like if I uninstalled it from control panel, it just removes the uninstall entry from the reg...or does this auto uninstall the previous version?
Woka
My question is ....
Who is doing all this deleting? Are your users going to go into the registry and delete the keys? Is that what you are worried about. You are right deleting the keys will NOT delete the corresponding files (no way). But why are you worried about this? Users should just click the "Uninstall" button. When they click that INNO gets rid of all component files, references, and the [Registry] section in INNO gets rid of the registry entry. So that when it is installed next time you dont get the weird BadgerIs1
Hmmm...gonna leave this reg problem for a few days.
Anyways, back to my original q. about IIS. I still can't get it to work with anything but the admin account
Attached to this, and the following post are screen shots of my current settings. They require a log in
If I rename the anon user account to the admin acount then it works.
But, the default IIS anon user account was the same permission groups as the user Brucy.
Am I missing something?
Does a user have to be part of a certain permission group or something?
Resolved.
For some reason windows messed up I think.
I created all the directories and the txt file web site all within 2 mins of each other. I checked the security of the folders and they said everyone has read access. I didn't think about my index.htm file. Just checked it and for some reason it only had the admin user who can do anything with it
Why was the files security policies different?
I didn't manually change them.
Anyways now it allows a normal user to be used as anon access.
Reply With Quote
