I want to enable banner while users accessing my machine through telnet. I know how to achieve it through ssh http://servercomputing.blogspot.in/2012/01/how-to-add-ssh-login-banner.html
I think you have to edit
/etc/issue.net
/etc/issue is the text that is displayed before any user is able to log on the system.
Or you can edit
/etc/motd
Which displays after you log in
If your system telnet server is using pam login module, you can use following steps to enable telnet banner.
Add (uncomment) following lines in "/etc/pam.d/login"
auth required pam_issue.so issue=/etc/issue noesc
After this configuration, text from file "/etc/issue" is displayed as banner.
Make sure pam_issue.so library is present in your system library folders.
Related
This seems like a simple question but I can't find an answer. I use MobaXterm free edition to SSH into my machines. Every time I SSH into a machine the side bar automatically expands with the paths on the remote machine. I don't need this side bar and every time I have to collapse it. Is there a way to permanently disable the side bar or at least not automatically expend it when SSH-ing?
Here is a picture (linked) of the expaned sidebar:
Under settings there are these 2 settings that control this that I typically turn off.
While instructing users through the GUI settings is an option it is often desirable to implement the application with an already usable default configuration. These settings are stored in the MobaXterm.ini file.
Hints for locating this file can be found here: Mobaxterm configuration settings
I'm using windows and mine was in my Documents/Mobaxterm folder
Here are the configuration settings I use to remove the sidebar and set the app to compact mode:
[WindowPos_xxxxxxxxxxxxx]
...
CompactMode=0
SidebarVisible=0
...
[SSH]
...
AutoStartSSHGUI=0
EnableSFTP=0
...
In newer versions of MobaXterm (v21.3 as of this writing), as an alternative to adjusting MobaXterm.ini file as mentioned in the other answer, it could be disabled by changing Session settings 🡺 Advanced SSH settings 🡺 SSH-browser type from SFTP Protocol 🡺 None
I have restarted our google cloud compute engine instance, however after the restart ssh is no longer working and giving connection refused.
I have verified and the ssh keys are configured for the users, and firewall rules are open for ssh.
Is there any other method I can use to try and resolve this?
The first thing to do is to check the Serial console output of the machine to determine if the SSH daemon has started or not. That log can be accessed from the Developer Console.
If you couldn't ssh to the instance you can follow the below step to access the instance from the serial console:
Connect to the instance using the serial console
1. Go to the VM instances page in Google Cloud Platform console.
2. Click on the instance for which you want to add a startup script.
3. Click the Edit button at the top of the page.
4. Click on ‘Enable connecting to serial ports’
5. Under Custom metadata, click Add item.
6. Set 'Key' to 'startup-script' and set 'Value' to this script:
#! /bin/bash
useradd -G sudo USERNAME
echo 'USERNAME:PASSWORD' | chpasswd
7. Click Save and then click RESET on the top of the page. You might need to wait for some time for the instance to reboot.
8. Click on 'Connect to serial port' in the page.
9. In the new window, you might need to wait a bit and press on Enter of your keyboard once; then, you should see the login prompt.
10. Login using the USERNAME and PASSWORD you provided.
I have tried following this tutorial but the new password doesn't take effect after security is enabled again, still have to use old password to login as wasadmin:
http://weblogic-wonders.com/weblogic/2014/03/27/reset-websphere-admin-console-password/
I even tried the guide from IBM:
http://www-01.ibm.com/support/docview.wss?uid=swg21392427
But I'm lost at this step:
_Navigate via command prompt to /ConfigEngine
Because in my WebSphere it doesn't have this ConfigEngine folder in order the run the rest of the commands.
Can anyone help me?
EDIT: This is WebSphere 7 for Maximo 7.5
Have you tried the following?
To disable security, please perform the following steps via wsadmin:
/bin/> wsadmin -conntype NONE
wsadmin> securityoff
wsadmin> exit
Restart the servers.
Enable the security from administrative console.
Once the needed corrections are made, you can re-enable security in the admin console and then restart WebSphere.
NOTE: To restart the servers, you will first need to manually kill the java process since security is still enabled in the currently running process.
Or editing the xml file
Following this link you have 2 optiont:
This is for the standalone version
Make a backup of the security.xml file:
/config/cells/cellname/security.xml
Edit the security.xml file by searching for the first instance of " enabled= ". You should see enabled="true" as in:
Change to enabled="false".
Save the security.xml file.
Restart server1 and the WebSphere_Portal servers. If you get authentication exceptions while trying to stop the servers, you may have to manually kill the server processes and then restart them.
In the wpconfig.properties file, make the following changes:
PortalAdminId=wpsadmin
PortalAdminGroupId=wpsadmins
Refer to the Information Center link for specific instructions.
Save the wpconfig.propeties file.
Try to disable security again using the disable-security task:
./WPSconfig.sh disable-securit y
At this point, security should be disabled. You can verify by accessing the WebSphere Application Server admin console. You should be prompted for only a user name, not a password.
Follow these instructions for a clustered version:
Make a backup of the security.xml file on the Deployment Manager machine:
/config/cells/cellname/security.xml
Edit the security.xml file by searching for the first instance of "enabled= ". You should see enabled="true" as in:
Change to enabled="false".
Save the security.xml file.
Copy the security.xml file to the nodes:
/config/cells/cellname/security.xml
/config/cells/cellname/security.xml
Restart DMGR, NodeAgents, and WebSphere_Portal servers. If you get authentication exceptions while trying to stop the servers, you may have to manually kill the server processes and then restart them.
In wpconfig.properties, make the following changes:
PortalAdminId=wpsadmin
PortalAdminGroupId=wpsadmins
Refer to the Information Center link for specific instructions.
Save the wpconfig.propeties file.
Try to disable security again using the disable-security task. Note that the DMGR and the nodeagent should be running:
./WPSconfig.sh disable-security
At this point, security should be disabled. You can verify by accessing the DMGR AdminConsole. You should be prompted for only a user name, not a password.
Or more option is explained here
Note: I haven't tried this myself yet
Goto DMGR bin directory and follow the below process.
[root#localhost bin]# ./wsadmin.sh -connType NONE -lang jython
wsadmin>AdminTask.changeFileRegistryAccountPassword('-userId saddam -password saddamm')
wsadmin>AdminConfig.save()
Please restart dmgr.
If you have forgotten the password, then you have to directly kill the dmgr process id and start dmgr.
Login to WebSphere Console -> Users and Groups -> Manage Users -> click on <user_name> -> change the password value -> save the configuration.
I'm running a mongodb process with the following line:
/usr/bin/mongod --dbpath /var/db/mongo --journal
According to mongodb's docs:
http://www.mongodb.org/display/DOCS/Http+Interface
I should be able to access the http console with http://myhost:28017
When I attempt to access the page it asks for authentication.
According to the docs if security is configured I would need to authenticate. But after looking at mongodb.org/display/DOCS/Security+and+Authentication it seems clear to me I'm not using any authentication. I don't run the process with the --auth option, nor are there any users when I run a db.system.users.find() command.
What's going on here?
I have been able to reproduce this, and this is not the intended behavior. I have filed https://jira.mongodb.org/browse/SERVER-4601 The fix version is 2.1.1
Thank you for bringing this to our attention!
In the meantime, there are two work-arounds:
1) Enter the credentials for authentication in the browser pop-up window
2) Remove all user credentials from each of your DBs (including admin) using db.system.users.remove()
Either of these should allow you to view the http console.
Greetings Brain,
i am using mongo V 2.4.6 and its on default port 27017, its http console is enabled by default but when you try to access from Network it ask for password and i dont know why as i am new to this and dont know the exact reason. by i have a way to access it.
Create a tunnel to your mongo Server and when you access, it wont ask for password. and if you are using putty.
enter host name
go to ssh on left menu options and click +
Than Click on tunnel
in Source port type 28017
in destination type localhost colon port 28017(sorry dont know how to write http url in localhost here in my post)
not click open and provide ssh username and password
now open browser on PC from where you are doing ssh .Type localhost and port 28017
and Boom its accessible and wont ask for username and password. hope it work for you, let me know if u need any help.
I got a CVS connection string, here it is :
:ssh;username=dummy;password=dummy;hostname=repos.mooo.com:/home/projects/repos
How can I get project code using WinCvs, I've just installed it and I can't find howto online, maybe some help, thank you
In WinCVS 2.1, Click the Remote menu item, and select Checkout code.
On this screen click the ... next to CVSROOT, and you should bring up a dialog allowing you to enter the parameters you mention in your question (this is a bit easier to do than trying to enter the string manually).
You'll also need to enter a module name on the server, and a directory to check our the code into, but once you do this and click OK you should start checking out the code.
You have to use WinCVS with the PuTTY SSH tools to be able to connect securely. Check out the description here
The site covers the following steps
Download the required materials (WinCvs, PuTTY).
Install the PuTTY SSH suite.
Install WinCvs.
Generate a SSH key pair.
Upload your SSH key pair.
Configure Pageant (a component of PuTTY).
Test your automated authentication.
Configure WinCvs.
Start using WinCvs