I have Tortoisehg set up with a clone of a remote repository on Bitbucket, using https protocol. I turned on the mercurial_keyring extension, and it took care of password handling just fine. Until one day it didn't. Every time I commit now, on push-after-commit it pops up and asks me for a password.
I carefully changed the password on the server, and started typing in that password when asked. IT DOESN'T HELP! It doesn't accept that password.
I hit cancel when asked for the password. Then I go and press the Push green arrow button at the top right of the screen. After asking for confirmation – IT GOES! No password required!
There are three computers that connect to this particular Bitbucket repository. For a while two of the three were working fine without asking a password. Then another one started asking! And then a third popped up asking for something different: "You need to identify yourself to the server." Once again, cancel, use the Push button, works fine!
I am so confused. Has anyone seen this, has anyone fixed it?
BTW, the remote repository is nowhere mentioned in my tortoisehg settings, but it is in my hgrc file:
[paths]
default = https://joymaker3#bitbucket.org/joymaker3/my-repo-name
I yjink, you have to re-read at least section 3.2. "Repository configuration (HTTP)" of extension wiki and check related settings of all repos:
good (full) URL in [paths]
only needed data (if needed) in [auth] (no password for configured remote repository)
you can also enable debug in TortoiseHG and inspect output on failed push
Related
For example I'd like to see this as a feature if it does not already exist.
Hence my question.
This should be tracked with gitlab-ce issue 18601, but for a private GitLab server, not necessarily gitlab.com.
See commit cfd5870
When you choose to allow only one of the protocols, a couple of things will happen:
The project page will only show the allowed protocol's URL, with no option to
change it.
A tooltip will be shown when you hover over the URL's protocol, if an action
on the user's part is required, e.g. adding an SSH key, or setting a password.
I used bitbucket a lot in the past (mostly because of the private repos). Have not used it for a while and now I always get "fatal: Authentication failed" error when trying to clone a repo. I feel it may be related to this whole Atlassian thing because now I cannot find how to configure bitbucket user password, only Atlassian password. That's why I am asking: is there some other bitbucket user password and is there any way to change it?
All I see after clicking in the upper right corner when logged in bitbucket is "Manage Atlassian account, View profile, Bitbucket settings, Integrations, Log ot". Password changing is only located in "Manage Atlassian account".
This what I've done so far (without success):
changed password (several times, now it consists of the small letters only)
played with variations of URL (with/out username, adding password to url)
deleted bitbucket account and created a new one (however, connected to the same Atlassian account as before)
tested via different networks at home/work.
Nothing worked so far. The same result on different computers (Windows and Linux). In the same time I can clone Github repos and work with them as usual. I need HTTPS only.
You likely need to configure your SSH keys properly. Login to Bitbucket through the web browser. Click on your icon in the top right corner and click on Bitbucket Settings from the pop-up menu. On the next screen will be a Settings menu on the left hand side. Click on SSH keys. If you already have SSH keys setup on your computer you can add your current keys. If you don't you'll need to create some keys, usually done with the ssh-keygen command line tool. This should generate two files, id_rsa and id_rsa.pub. Open the id_rsa.pub file and copy the contents to your clip board. Back in your web browser click the Add Key button. Give it a label and paste the contents of your clipboard into the Key text box.
You'll need to make sure git is set to use this key when you connect either through an SSH config file.
Everything works after creating a brand new user for both Bitbucket and Atlassian with another email.
Okay, I know it may sound stupid but I really need your opinions or suggestions about something. A computer has an older WAMP version (5 1.7.0) installed in it (I'm not the one who installed it) and running on Windows XP. Whenever I go to its Phpmyadmin page, it automatically gives me access to anything what are in it. That's a security hole that must be solved. I want it to ask me or prompt a login page first. I still have no success from the following steps that I've tried:
I have set the username as root and the password as
samplepass from the Priveleges section in the Phpmyadmin page - Still no success!
I also modified the config.inc.php file. I put the said password in $cfg['Servers'][$i]['password'] and changed the "cookie" as "config" in $cfg['Servers'][$i]['auth_type'] - Still no success!
Already restarted the connection of all WAMP services after the changes made - Still no success!
I also cleared the histories, caches, cookies, etc. in the browsers just incase - Still no success!
One thing I've noticed is that the file has no $cfg['Servers'][$i]['AllowNoPassword'] nor $cfg['Servers'][$i]['AllowNoPasswordRoot'] in it. I tried including that into the file and providing it the value as "YES" but still, no login page is displaying.
I don't want to reinstall the WAMP or install new one. I'm afraid to destroy what was already there. So what do you think why the login page is still not displaying? Am I forgetting something or missed to do? (Sorry for sometimes I'm forgetful).
Alright, just after trying the things out again with still no success, I came up with this:
I changed back the value of $cfg['Servers'][$i]['auth_type'] from "config" to "cookie"
Then I added a random text value for $cfg['blowfish_secret']
After the (2) changes I made, I restarted the all the services again and poof! Login page is now displaying! But I'm still confused why my first tries didn't work. I'm not a know-it-all person about this particular area and sure there's more things to know about database thing. That's all.
I have Webmin installed on 5 or 6 servers but a few months back decided to install two-factor authentication for logging into Webmin using Google Authenticator app on my phone.
To my surprise, I lost all my tokens in the Google Authenticator app when I changed phones. This actually happen to me twice. I have rebuilt everything everywhere else but can no longer log into Webmin on this one server.
I tried searching Google to death but no answers. I tried uninstalling Webmin and re-installing using RPM.
After re-installing Webmin it just keeps the same settings which means I still need the Google Auth token which is no longer on my phone.
Any ideas?
Should I try to break the Oauth module I think it needs to work or will this cause me more problems?
Fond this here:
http://sourceforge.net/p/webadmin/discussion/600155/thread/512d81e9/
Go into this file /etc/webmin/miniserv.conf, delete this line:
twofactor_provider=totp
And, in /etc/webmin/miniserv.users, there is this line.
root:x:0:::::::0:0:totp:HBL7W4RTG8T6FG8W:
I just deleted the totp so the line read:
root:x:0:::::::0:0::HBL7W4RTG8T6FG8W:
Saved the file and restarted webmin: service webmin restart.
I could then log back in with un/pw and generated my QR code.
Even Simpler Fix:
0:0:totp:HBL7W4RTG8T6FG8W:
The "HBL7W4RTG8T6FG8W" between the colons is your KEY for Google Auth!
When using Google authenticator you can enter a KEY or use QR Code. Just create a new Google auth account and use THAT KEY.
DONE! No need to restart anything.
Enjoy!
C0l. P.
Run the following to remove two factor authentication:
sed -i 's/totp//g' /etc/webmin/miniserv.users
sed -i '/twofactor_provider=totp/d' /etc/webmin/miniserv.conf
/etc/init.d/webmin restart
I realise this is a little late but I thought I'd post it nonetheless for anyone who is interested.
The entry in /etc/webmin/miniserv.users should be a TOTP secret in Base32 format.
So to log in simply run :
oathtool --totp -b 'SECRET' -v
Where SECRET is the code between the quotes and it will spit out your Two-factor token enabling you to log in.
The -b says your giving it the SECRET in Base32 (Hex is the default).
Then goto "Webmin->webmin Users" to disable TFA and re-enable it in the normal way.
Or if you want, you can use "qrencode" to re-create your google-authenticator setup without having to change the secret (handy if a group are sharing the same SECRET ...bad idea!! but this will save your bacon if one of you gets locked out).
$ qrencode -o ~/.totp-key.png "otpauth://totp/?secret=BASE 32 SECRET&issuer=Your name, etc."
NB. "oathtool" using the -v option allows you to see the SECRET in both Base32 and HEX so you can use either as necessary to setup any TFA app.
Also ensure that the machine you use has it's time sync'd correctly!
QED.
I disabled 2FA, then I was unable to login, not only from webmin from ssh with password as well.
I applied #Todd 's advice, after restarting webmin I was totally unable to see the main login page.
Luckily I had some other session already open. I used the command below to change the password for root user, restarted webmin, all was ok.
/usr/share/webmin/changepass.pl /etc/webmin root myNewPassword
Note: Apply at your own risk. I had backups, so I did not need to worry. My server OS is Ubuntu 14.04
I'd like to know how to get Subversion to change the name that my changes appear under.
I'm just starting to use Subversion. I'm currently using it to version control code on an XP laptop where I'm always logged in under my wife's name. I'd like the subversion DB to show the changes under my name.
Later on I'll replicate the DB so it is accessible to the whole house. My wife uses the office computer where she is always logged in under my name. I'll probably set it up so that it automatically checks in modified documents... preferably under her name.
Eventually I'll probably be using it from a linux machine under another username.
Is there some way to modify the user environment to change the user name that Subversion calls you? I'd expect something like setting SVN_USERNAME='Mark' which would override however it usually gets the name.
Update: It looks like the --username flag that Michael referred to does work to change the name reported by "svn stat", even for local file: repositories. In addition, it is sticky so you don't need to specify it for the next command. I even rebooted and it still used the "--username" value from my previous boot.
Most Subversion commands take the --username option to specify the username you want to use to the repository. Subversion remembers the last repository username and password used in each working copy, which means, among other things, that if you use svn checkout --username myuser you never need to specify the username again.
As Kamil Kisiel says, when Subversion is accessing the repository directly off the file system (that is, the repository URL is of form file:///path/to/repo or file://file-server/path/to/repo), it uses your file system permissions to access the repository. And when you connect via SSH tunneling (svn+ssh://server/path/to/repo), SVN uses your FS permissions on the server, as determined by your SSH login. In those cases, svn checkout --username may not work for your repository.
For svn over ssh try:
svn list svn+ssh://[user_name]#server_name/path_to_repo
svn will prompt you for the user_name's password.
You can setup a default username via ~/.subversion/servers:
[groups]
yourgroupname = svn.example.com
[yourgroupname]
username = yourusername
Please be aware that older versions of svn do not support it (e.g. 1.3.1 [sic!]).
"svn co --username=yourUserName --password=yourpassword http://path-to-your-svn"
Worked for me when on another user account. You will be prompted to enter username/password again though. You need to login like the above once and you are all set for the subsequent times(Unless you restart your machine).
If you need to specify a username other than your logged in user for use with svn+ssh just add an entry to your .ssh/config file:
Host example.com
User jdoe
Subversion usually asks me for my "Subversion username" if it fails using my logged in username. So, when I am lazy (usually) I'll just let it ask me for my password and I'll hit enter, and wait for the username prompt and use my Subversion username.
Otherwise, Michael's solution is a good way to specify the username right off.
Most of the answers seem to be for svn+ssh, or don't seem to work for us.
For http access, the easiest way to log out an SVN user from the command line is:
rm ~/.subversion/auth/svn.simple/*
Hat tip: http://www.yolinux.com/TUTORIALS/Subversion.html
Using Subversion with either the Apache module or svnserve. I've been able to perform operations as multiple users using --username.
Each time you invoke a Subversion command as a 'new' user, your $HOME/.subversion/auth/<authentication-method>/ directory will have a new entry cached for that user (assuming you are able to authenticate with the correct password or authentication method for the server you are contacting as that particular user).
I believe if you use the file:// method to access your subversion repository, your changes are always performed under the user which accesses the repository. You need to use a method that supports authentication such as http:// or svn://.
See http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.serverconfig.choosing
If you are using svn+ssh to connect to the repository then the only thing that authenticates you and authorizes you is your ssh credentials. EVERYTHING else is ignored. Your username will be logged in subversion exactly as it is established in your ssh connection. An excellent explanation of this is at jimmyg.org/blog/2007/subversion-over-svnssh-on-debian.html
Go to ~/.subversion/auth/svn.simple/*, and you will see a list of files that contains the information about your svn user account. Just delete all others that you don't need.
After that, when you do anything that regards to SVN operation, such as commit, rm, etc,. You will be prompt again to enter username or passwords.
TortoiseSVN always prompts for username. (unless you tell it not to)
I believe you can set the SVN_USER environment variable to change your SVN username.