The first example of SQL injection can be seen on line 13. In the request, you are supposed to supply a username and password. However, as you can …
Tag: password
unknown uninstall password
I do not need a solution (just sharing information)
hello,
I am looking for assistance regarding the uninstall password. We need to uninstall symantec but arre unable to because we do not have the uninstall. An alternative methods would be appreciated. Thanks.
0
Related:
Policy Center change in 1.1.5.5 – PS Passwords Shareable
I do not need a solution (just sharing information)
Starting with 1.1.5.1 PolicyCenter by default does not allow you to push touch or look passwords to the PacketShapers due to security concerns. However, this is a problem as one cound guess. To change the behavior back to sharable you have to do the following (from support):
There is a security risk with enabling the password push feature, which is why it has been disabled. The only way to re-enable it is on a case by case basis, as Symantec will require the serial number of the PolicyCenter. Using this serial number, a request will be made to Engineering to create an enablement key, which will then be provided to Support. Support will then provide the enablement key to the customer along with the following instructions:
- Access the PolicyCenter CLI.
- Enable debug mode: pc showdebug 1
- Enter the enablement key you were provided: pc enablepushpw <enablement key>
- Disable debug mode: pc showdebug 0
This PolicyCenter unit will now be able to centrally manage passwords for all PacketShapers that are registered to it.
Rick
0
Related:
Symantec Encryption Desktop Professional 10.4.2
I need a solution
Hi,
I have Symantec Encryption Desktop Professional 10.4.2 without license & i forgot the passphrase & all passwords related
is There any Solution for this case?
Thank you
0
Related:
nFactor – Customizing UI to Display Images
This solution contains two parts – loginSchema extension and custom script to process the extension.
LoginSchema extension
In order to get control over the rendering of the form, a custom ‘id’/’credential’ is injected into loginSchema. This can be done by reusing existing schema and adding one. In this example, we would take a loginSchema that has only one text field (such as /nsconfig/loginschema/LoginSchema/OnlyPassword.xml) and customize it. below is the snippet that could be added. Complete loginSchema is described later in this article.
<Requirement><Credential><ID>swivel_cred</ID><Type>swivel_cred</Type><Input><Text><Hidden>true</Hidden><InitialValue>${http.req.user.name}</InitialValue></Text></Input></Credential></Requirement>
In the above line, we have specified “swivel_cred” as “Type” of the credential. Since this is not recognized as a builtin ‘credential’, UI looks for a handler for this type, and calls it if it exists.
We have also sent an initial value for this credential that is an expression that NetScaler dynamically fills. In this case, we are filling this with user’s name. In this example, it is used to notify swivel server of the username. It might not be needed all the time or it would have to be augmented with some other data. Those details have to be added as required.
Javascript to handle custom credential
When UI finds a custom credential, it looks for handler. All custom handlers are written in /var/netscaler/logon/LogonPoint/custom/script.js for default portal theme. For custom portal themes, script.js could be found in /var/netscaler/logon/themes/<custom_theme>/.
We add below script to render markup for our custom credential:
CTXS.ExtensionAPI.addCustomCredentialHandler({ // The name of the credential, must match the type returned by the server getCredentialTypeName: function () { return "swivel_cred"; }, // Generate HTML for the custom credential getCredentialTypeMarkup: function (requirements) { var div = $("<div></div>"); var image = $("<img/>"); var username = requirements.input.text.initialValue; //Get the secret from the response image.attr({ "style" : "width:200px;height:200px;", "id" : "qrcodeimg", "src" : "https://myswivelserver.citrix.com:8443/pinsafe/SCImage?username=" + username }); div.append(image); return div; }});
In the above snippet, we are handling the markup for ‘swivel_cred’. Credential name highlighted should match the ‘type’ specified earlier in the loginSchema extension.
When asked to generate markup, we are adding an image whose source points to swivel server. Once this is done, UI loads image from specified location. Since our loginSchema also has a textbox, UI renders that text box.
Administrator can modify “style” of image element to resize the image. Currently it configured for 200×200 pixels.
Configuration
nFactor configuration is better constructed bottom-up, ie the last factor first. This is because when you try to specify ‘nextFactor’ for the previous factors, you will require the subsequent factor’s name.
Swivel factor
>add loginschema swivel_image –authenticationSchema /nsconfig/loginschema/SwivelImage.xml
Download SwivelImage.xml from Full Loginschema section:
>add authentication policylabel SwivelFactor –loginSchema swivel_image
>bind authentication policylabel SwivelFactor –policy <policy-to-check-swivel-image> -priority 10
Psuedo Factor for group check
>add authentication policylabel GroupCheckFactor
>add authentication policy contractors_auth_policy –rule ‘http.req.user.is_member_of(“contractors”)’ –action NO_AUTHN
>add authentication policy not_contractors _auth_policy–rule true –action NO_AUTHN
>bind authentication policylabel GroupCheckFactor –policy contractors_auth_policy –pri 10 –nextFactor SwivelFactor
>bind authentication policylabel GroupCheckFactor –policy not_contractors_auth_policy –pri 20
First factor for Active Directory login
>add ldapAction <>
>add authentication policy user_login_auth_policy –rule true –action <>
>bind authentication vserver <> -policy user_login_auth_policy –pri 10 –nextFactor GroupCheckFactor
In above configuration, we technically specified three factors of which one is implicit/pseudo.
The above nFactor configuration can also be achieved using nFactor visualizer, this feature is available from 13.0
The above nFactor flow can be visualized as follows,
Configuration Through Visualizer:
1. Go to Security –> AAA – Application Traffic –> nFactor Visualizer –> nFactor Flows –> Click Add
2.Click on the + sign to add the nFactor Flow
3. Add Factor, this will be the name of the nFactor Flow,
4. Add the schema for the First Factor by clicking on the Add Schema and then Add,
5. Select the first factor login schema i.e for LDAP username and password only, if none exist then you can create one as below, click on create.
6. Click on Add Policy, Select the LDAP authentication policy, click on Add
If you do not have the above LDAP policy, you can create the same by clicking on the Add button corresponding to the select policy drop down list in the above snapshot.
In case the LDAP server is not added on the ADC, click on Add action, please refer to this article to add the LDAP server on the ADC (https://support.citrix.com/article/CTX108876)
7. Add a Decision Box, to check if the users belong to Internal-Group or Contractor group,
8. Click on Add Policy to add a policy to check the group membership,
Similarly, create another policy in the same decision box to check for Contractor group,
9. In case the user belongs to Contractor Group, then we need to have another factor i.e Swivel for such users, Add one more factor for Swivel, Click on Create,
10. Add the Swivel login schema and the policy for the Swivel Image,
Full Loginschema
Below is an example schema with swivel credential and a text box. Care must be taken when copying data for web browser. Quotes might be shown differently. It is recommended to copy in editors like notepad before saving them to files.
<?xml version="1.0" encoding="UTF-8"?><AuthenticateResponse xmlns="http://citrix.com/authentication/response/1"><Status>success</Status><Result>more-info</Result><StateContext></StateContext><AuthenticationRequirements><PostBack>/nf/auth/doAuthentication.do</PostBack><CancelPostBack>/nf/auth/doLogoff.do</CancelPostBack><CancelButtonText>Cancel</CancelButtonText><Requirements><Requirement><Credential><ID>swivel_cred</ID><Type>swivel_cred</Type><Input><Text><Hidden>true</Hidden><InitialValue>${http.req.user.name}</InitialValue></Text></Input></Credential></Requirement><Requirement><Credential><ID>passwd</ID><SaveID>ExplicitForms-Password</SaveID><Type>password</Type></Credential><Label><Text>Password:</Text><Type>plain</Type></Label><Input><Text><Secret>true</Secret><ReadOnly>false</ReadOnly><InitialValue></InitialValue><Constraint>.+</Constraint></Text></Input></Requirement><Requirement><Credential><Type>none</Type></Credential><Label><Text>Hello ${http.req.user.name}, Please enter passcode from above image.</Text><Type>confirmation</Type></Label><Input /></Requirement><Requirement><Credential><ID>saveCredentials</ID><Type>savecredentials</Type></Credential><Label><Text>Remember my password</Text><Type>plain</Type></Label><Input><CheckBox><InitialValue>false</InitialValue></CheckBox></Input></Requirement><Requirement><Credential><ID>loginBtn</ID><Type>none</Type></Credential><Label><Type>none</Type></Label><Input><Button>Log On</Button></Input></Requirement></Requirements></AuthenticationRequirements></AuthenticateResponse>
Example output
Once above configuration is performed, image should be displayed like below. Image height, placement can be altered in the javascript mentioned above.
Related:
How to uninstall Symantec Cloud Endpoint Protection without Password
I need a solution
Hi,
I am trying to uninstall Symantec.cloud – Cloud Agent version 3.00.31.2817 and Symantec.cloud – Endpoint Protection Version NIS-22.8.0.50. It is prompting for a password and no one knows what the password is. How can I remove this without knowing the password.
0
Related:
Sophos Anti-Virus for Linux and UNIX: How to set up the update sources from the command line
1 to view and record the current setup:> 1
Primary update source address = \SEC6SophosUpdateCIDsS000savlinux
Primary update cache path = /opt/sophos-av/update/cache/Primary
Primary update source username = testdomSophosUpdateMgr
Primary update source password = ********
Update period minute = 60
[1] Display update configuration
Configure primary update source:
[2] From Sophos
[3] From own server
Configure secondary update source:
[4] From Sophos
[5] From own server
[q] Quit
What do you want to do? [1]
Related:
Windows 10 April 2018 Update (v1803) – Citrix Known Issues
Issue 5
Issue Description
Pin prompt for Smart card authentication is not available to login into VDA session. User is prompted for “Username” and “Password” instead of Smart card PIN to login into VDA session.
[HDX-13195]
Problem Cause
Microsoft has changed the way Smart Card Service (SCardSvr) works in Windows 10 v1803. The service will run only if a Smart Card reader is connected. As ICA sessions redirect the Smart Card, it finds the service not to be running and fails.
Solution
This issue would not be encountered if earlier Windows 10 machine with VDA installed is upgraded to 1803. For a clean install of Windows 10 v1803, Microsoft has provided a mechanism to enable to enable Smart Card Service (SCardSvr) by adding a registry key. To add the registry key, follow below steps on the VDA:
Caution! Refer to the Disclaimer at the end of this article before making changes to Registry
-
Right click on Start button and choose Run
-
Type ‘Regedit’ and click Ok.
On x86 machine, browse to HKEY_LOCAL_MACHINE -> Software -> Microsoft -> Cryptography -> Calais
On x64 machine, browse to HKEY_LOCAL_MACHINE -> Software -> WOW6432Node -> Microsoft -> Cryptography -> Calais -
Right click on Calais in left pane, choose New -> DWORD (32 bit) value.
-
Enter the value as ‘AllowServiceAccessWithNoReaders’ and hit enter.
-
Double click on ‘AllowServiceAccessWithNoReaders’ and enter the value as 1.
-
Close Registry Editor and restart the machine.
Issue 6
Issue Description
Print command from inside an ICA session of Windows 10 v1803 client fails to print using mapped Citrix UPS configured XPS Printer.
[HDX-13664]
Problem Cause
XPS Viewer is not available on Windows 10 v1803 by default. It is available as a Feature on Demand.
Solution
To install XPS Viewer, follow the below steps:
- Open Command Prompt in elevated mode
- Run the command “Dism /online /add-capability /CapabilityName:XPS.Viewer~~~~0.0.1.0”
Note:
- The machine should be connected to the Internet for above command to acquire and install XPS Viewer.
- While upgrading from earlier Windows 10 version to v1803 using ISO, if option ‘Download and install updates’ is chosen XPS Viewer will be retained after upgrade.
Issue 7
Issue Description
Citrix Workspace Environment Management (WEM) Agent fails to work when Windows 10 is upgraded to v1803.
[TPV-1184]
Problem Cause
The ‘Norskale’ key under [HKLM -> System -> CurrentControlSet -> Control] is removed during the upgrade to v1803.
Solution
Citrix is working with Microsoft to resolve this issue. To restore functionality, users could uninstall WEM Agent on the upgraded machine, reinstall and reconfigure.
Issue 8
Issue Description
Some maximized applications in Local App Access(LAA) enabled desktop sessions cannot be minimized using the minimize button. (Example application: Notepad, CMD)
[LC8813]
Problem Cause
The issue is due to an incorrect function call getting triggered for LAA enabled desktops.
Solution
This issue is resolved in Citrix XenDesktop 7.18 and CU2 for XenDesktop 7.15.
Issue 9
Issue Description
Citrix User Profile Manager (UPM) stops working after Windows 10 is upgraded to v1803.
[TPV-1307]
Problem Cause
The upgrade process is removing some of the registry entries related to UPM.
Solution
This issue is fixed with the Microsoft’s March 2019 Updates for Windows 10. Install the respective March 2019 update OR its replacement on your existing Windows 10 version before upgrading to Windows 10 v1803.
Issue 10
Issue Description
With Windows 10 v1803 as PVS Target Device (PVS 7.15 CU2), when Cache Type for vDisk is set as ‘Cache in device RAM’, a BSOD is encountered while booting.
[PVS-3634]
Problem Cause
This issue could be due to Kernel changes made in Windows 10 v1803 which might be preventing the Citrix PVS bootstrap and drivers from using reserved memory for RAM cache.
Solution
Citrix is investigating this issue. As a workaround, “Cache in device RAM with overflow on hard disk” option can be used.
Note: Windows server 2019 has the same issue. This only affects Legacy bootstrap PXE booting, which includes BDM and ISO booting. Using UEFI bootstrap works fine, including UEFI BDM and ISO booting.
Issue 11
Issue Description
Virtual Smart Card Reader (created by tpmvscmgr.exe) stops functioning after Windows 10 is upgraded from v1709 to v1803 with Citrix VDA installed.
Problem Cause
The Windows Upgrade process is rendering the Virtual Smart Card Reader non-functional. This issue is not encountered with a fresh install of Windows 10 v1803
Solution
Citrix is investigating this issue. As a workaround, users could login to the VDA using user name and password, go to the Device Manager and disable the Virtual Smart Card Reader and enable it again. This can also be done programmatically via Powershell with the following:
From a PoSH session run “Get-PnpDevice | ft FriendlyName,InstanceID”
In the Output match the friendly name with the name in device manager and also the one given when it was created with tpmvscmgr.exe. The InstanceID should look something like ROOTSMARTCARDREADER000
Once the InstanceID is identified the cmdlets to enabledisable the device are relatively simple:
Disable-pnpDevice –InstanceID ROOTSMARTCARDREADER000 –Confirm:$false
Enable-pnpDevice –InstanceID ROOTSMARTCARDREADER000 –Confirm:$false
Running a script with these cmdlets restores the Virtual Smartcard to a working state and could be incorporated into a startuplogon script.
References:
https://docs.microsoft.com/en-us/powershell/module/pnpdevice/get-pnpdevice?view=win10-ps
https://docs.microsoft.com/en-us/powershell/module/pnpdevice/disable-pnpdevice?view=win10-ps
https://docs.microsoft.com/en-us/powershell/module/pnpdevice/enable-pnpdevice?view=win10-ps
Issue 12
Issue Description
Pass-Through Authentication (SSON) fails to work when Windows 10 is upgraded to v1803 with Workspace App installed.
[TPV-1916]
Problem Cause
While upgrading to v1803, few registry entries required by SSON gets removed under HKLM > System > CurrentControlSet > Control > NetworkProvider.
Solution
Users may manually add the registry keys (Workaround 1) OR run a Power Shell script (Workaround 2) that adds the registry entries that were deleted by the installer.
Workaround 1:
Caution! Refer to the Disclaimer at the end of this article before making changes to Registry
-
Right click on Start button and choose Run
-
Type regedit and click OK.
-
Browse to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services.
-
Right-click on Services and choose New > Key.
-
Enter value PnSson for the new key and click OK.
-
Right-click the key PnSson for and choose New > DWORD 32 bit, enter IsEnabled and set Value data 1
-
Right-click the key PnSson for and choose New > DWORD 32 bit, enter Type and set Value data 4
-
After adding the keys and values, it should appear like below:
- Right-click the key PnSson and choose New > Key.
- Enter value NetworkProvider and click OK.
- Add the following entries under the newly created key:
-
Right-click NetworkProvider > New > String Value, enter Name and set Value data Citrix Single Sign-on.
-
Right-click NetworkProvider > New > String Value, enter ProviderPath and set Value data to below value:
C:Program Files (x86)CitrixICA Clientx64pnsson.dll on 64 bit Machine
C:Program FilesCitrixICA Clientpnsson.dll on 32 bit Machine
Note: If Workspace App is installed in Custom location, the above values should be changed accordingly to $InstallPath$ICA Client… Example: If install path is c:Citrix then the value should be C:CitrixICA Client….
-
Right-click NetworkProvider > New > DWORD 32 bit, enter Class and set Value data 2.
-
-
After adding the keys and values, it should appear like below:
-
Browse to HKEY_LOCAL_MACHINE> SYSTEM> CurrentControlSet> Control> NetworkProvider> Order
-
Right Click on ProviderOrder and Select Modify.
-
Add ,Pnsson to the end of the current value in the registry.
-
After adding the keys and values, it should appear like below:
-
Browse to HKEY_LOCAL_MACHINE> SYSTEM> CurrentControlSet> Control> NetworkProvider> HwOrder
-
Right Click on ProviderOrder and Select Modify.
-
Add ,Pnsson to the end of the current value in the registry.
-
After adding the keys and values, it should appear like below:
- Restart the machine.
Workaround 2:
Users could run the Power Shell script that adds the above entries. Download the attachment.zip file, extract it to a folder and run Receiver_SSON.PS1. This script will add the registry entries based on the Receiver install location. It also retains services registered with Microsoft Network Provider and appends PnSson value. Users are advised to test the script before using it in a production environment.
Related:
Password prompt
I do not need a solution (just sharing information)
A prompt pops up asking for the password or the certificate. We do not have the password. Is there anyway to disable the pop up prompt ? It Pop up everyday
0
Related:
administrator and limited administrator account is not working
I need a solution
Hi all,
I encounter a login problem for (administrator and limited administrator). My SEPM is integrated with AD, So, I thought it might be AD causing the problem but I created 3 admins(local) account with the different right. Only, the system administrator can successfully log in. The rest got a problem with an error message
The error message is as follow
Administrator’s user name or password is incorrect. Type a valid user name or password.
does anyone encounter this problem before??
0