Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 3283. (Read 9723787 times)
December 28, 2014, 11:07:19 PM
What are the top 3 VPS's for setting up masternodes? I used up my existing VPS IPs and now need some more.
December 28, 2014, 08:56:22 PM
You have the root password?
su -
su -
Yes - I have the root password, but when I use it the terminal returns "Authentication failure" which is understandable because I disabled root login.
I suppose I could delete the server and start again but then I'd need to understand the interaction a bit better between the root user and the 'login' user. I think if I give the login user admin privileges ('sudo' privilages) when I create it then that would probably solve it. Maybe that's the difference between Tao's guide and the others - he doesn't give the login user 'sudo' privileges when he creates it but he seems to simply do everything under root when he needs to.
Then my question is, who's home should the ~/.darkcoin directory be created in - is it always the 'login user' ?
Aw too late but if you have been blacklisted for whatever reason from the root access on ssh, vultr still gives you the chance of getting the root access by providing you a console on the vps manager page on vultr.com, just insert the root login.
Anyway if you are using a password access I reccomend you to install fail2ban to avoid bruteforcing, but I'd rather disable password login and use a restricted SSH key login, not so hard to setup.
December 28, 2014, 08:47:26 PM
31ST CHAOS COMMUNICATION CONGRESS OFFERS CONFIRMATION, SHOCKS
https://hacked.com/31st-chaos-communication-congress-offers-confirmation-shocks/
https://hacked.com/31st-chaos-communication-congress-offers-confirmation-shocks/
December 28, 2014, 08:29:50 PM
http://cointelegraph.com/news/113207/coinbase-is-tracking-how-users-spend-their-bitcoins
when will the masses(crypto masses) see the light?(DRK
)
when will the masses(crypto masses) see the light?(DRK
)Sometime in 2015, I am confident to say! Feel free to bookmark that comment.
December 28, 2014, 08:27:16 PM
Twitter down. 
LoL. Thanks, but I've just done exactly that
Jeez. There are so many ways of doing this. I'm learning more about Linux than I am about setting up masternodes (which is probably no bad thing).
In the end I just binned that last server and started again doing this:
- changed the root password to something complicated
- added a new user with "sudo useradd -s /bin/bash -g sudo -m
So that I had a login user that wasn't the root but that had "sudo" privileges. This time everything's going great - I can do it all with the loginuser and sticking "sudo" in front of everything.
I downloaded darkcoind from wget https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.10.17.24-linux.tar.gz
I "cd"d all the way into the expanded directories down to /64 and "mv"d darkcoind into /usr/bin. (Cos I quite like the idea of executables being in the bin directory and anyway, I think Linux looks there first f you just type 'darkcoind' without any leading directory).
Then I created ~/.darkcoin and now I'm going to do the darkcoin.conf and try to 'jiggbyDoThinxomoly' it with my local darkcoin.conf using a masternode genkey that I'll do on the Darkcoin QT on the Mac.
Sorry if this all sounds a bit cringeable to you Linux buffs but there just seem to be so many different ways of doing stuff in Linux and places where you can put stuff that I decided just to arbitrate on a few approaches.
P.S. I of course used Tao's ufw firewall commands to open 9999, limit port 22 to SSH access and close everything else. Also disabled root login according to chaeplin's original guide for EC2.
So my procedure is a kind of hybrid of Tao's and Chaeplin's.
Happy to see you got your VPS to work, toknormal. Yes, you are right that I prefer to log into root to perform functions like firewall. I'm happy you found something that works for you.
You don't need root to install/run/administer the daemon (unless you want to stick it in /usr/bin which is a waste of time IMO), just to set up the firewall and install any dependencies you need if you want to compile it yourself instead of downloading the binary.
LoL. Thanks, but I've just done exactly that
Jeez. There are so many ways of doing this. I'm learning more about Linux than I am about setting up masternodes (which is probably no bad thing).
In the end I just binned that last server and started again doing this:
- changed the root password to something complicated
- added a new user with "sudo useradd
So that I had a login user that wasn't the root but that had "sudo" privileges. This time everything's going great - I can do it all with the loginuser and sticking "sudo" in front of everything.
I downloaded darkcoind from wget https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.10.17.24-linux.tar.gz
I "cd"d all the way into the expanded directories down to /64 and "mv"d darkcoind into /usr/bin. (Cos I quite like the idea of executables being in the bin directory and anyway, I think Linux looks there first f you just type 'darkcoind' without any leading directory).
Then I created ~/.darkcoin and now I'm going to do the darkcoin.conf and try to 'jiggbyDoThinxomoly' it with my local darkcoin.conf using a masternode genkey that I'll do on the Darkcoin QT on the Mac.
Sorry if this all sounds a bit cringeable to you Linux buffs but there just seem to be so many different ways of doing stuff in Linux and places where you can put stuff that I decided just to arbitrate on a few approaches.
P.S. I of course used Tao's ufw firewall commands to open 9999, limit port 22 to SSH access and close everything else. Also disabled root login according to chaeplin's original guide for EC2.
So my procedure is a kind of hybrid of Tao's and Chaeplin's.
Happy to see you got your VPS to work, toknormal. Yes, you are right that I prefer to log into root to perform functions like firewall. I'm happy you found something that works for you.
December 28, 2014, 08:20:48 PM
Quote
Documents published by @DerSPIEGEL @laurapoitras @ioerror today reveal #NSA compromise SSH, SSL,TSL and store cryptographic handshakes #31c3
this will have a stronger effect on crypto than it probably appears on the first look.- eg. generating paperwallets via browser
Prying Eyes: Inside the NSA's War on Internet Security
http://m.spiegel.de/international/germany/a-1010361.html
December 28, 2014, 08:11:33 PM
http://cointelegraph.com/news/113207/coinbase-is-tracking-how-users-spend-their-bitcoins
when will the masses(crypto masses) see the light?(DRK)
when will the masses(crypto masses) see the light?(DRK
) December 28, 2014, 07:33:20 PM
December 28, 2014, 07:28:57 PM
there just seem to be so many different ways of doing stuff in Linux
Freedom is beautiful, eh?
December 28, 2014, 07:19:49 PM
You don't need root to install/run/administer the daemon (unless you want to stick it in /usr/bin which is a waste of time IMO), just to set up the firewall and install any dependencies you need if you want to compile it yourself instead of downloading the binary.
LoL. Thanks, but I've just done exactly that
Jeez. There are so many ways of doing this. I'm learning more about Linux than I am about setting up masternodes (which is probably no bad thing).
In the end I just binned that last server and started again doing this:
- changed the root password to something complicated
- added a new user with "sudo useradd
So that I had a login user that wasn't the root but that had "sudo" privileges. This time everything's going great - I can do it all with the loginuser and sticking "sudo" in front of everything.
I downloaded darkcoind from wget https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.10.17.24-linux.tar.gz
I "cd"d all the way into the expanded directories down to /64 and "mv"d darkcoind into /usr/bin. (Cos I quite like the idea of executables being in the bin directory and anyway, I think Linux looks there first f you just type 'darkcoind' without any leading directory).
Then I created ~/.darkcoin and now I'm going to do the darkcoin.conf and try to 'jiggbyDoThinxomoly' it with my local darkcoin.conf using a masternode genkey that I'll do on the Darkcoin QT on the Mac.
Sorry if this all sounds a bit cringeable to you Linux buffs but there just seem to be so many different ways of doing stuff in Linux and places where you can put stuff that I decided just to arbitrate on a few approaches.
P.S. I of course used Tao's ufw firewall commands to open 9999, limit port 22 to SSH access and close everything else. Also disabled root login according to chaeplin's original guide for EC2.
So my procedure is a kind of hybrid of Tao's and Chaeplin's.
December 28, 2014, 06:52:43 PM
As a general rule, never install software as root. As such, your user account would be the one with the darkcoin daemon running on it.
Thanks !
Am I right in thinking that to comply with this advice, Tao's guide would have to give 'sudo' privilages to the login user ? (Otherwise they can't do all the admin associated with installing the daemon).
You don't need root to install/run/administer the daemon (unless you want to stick it in /usr/bin which is a waste of time IMO), just to set up the firewall and install any dependencies you need if you want to compile it yourself instead of downloading the binary.
December 28, 2014, 06:38:59 PM
As a general rule, never install software as root. As such, your user account would be the one with the darkcoin daemon running on it.
Thanks !
Am I right in thinking that to comply with this advice, Tao's guide would have to give 'sudo' privilages to the login user ? (Otherwise they can't do all the admin associated with installing the daemon).
December 28, 2014, 06:32:32 PM
Next Litecoin dump incoming.
such a slow and painfull death of a coin... (we are talking about LTC).
You must be new in crypto
you just made a joke calling qwizzie a newbie. LTC was already dead that some of us even barely mention it long time ago. If you miss that escape time window at that moment, good luck, cause you will need it. December 28, 2014, 06:30:46 PM
You have the root password?
su -
su -
Yes - I have the root password, but when I use it the terminal returns "Authentication failure" which is understandable because I disabled root login.
I suppose I could delete the server and start again but then I'd need to understand the interaction a bit better between the root user and the 'login' user. I think if I give the login user admin privileges ('sudo' privilages) when I create it then that would probably solve it. Maybe that's the difference between Tao's guide and the others - he doesn't give the login user 'sudo' privileges when he creates it but he seems to simply do everything under root when he needs to.
Then my question is, who's home should the ~/.darkcoin directory be created in - is it always the 'login user' ?
As a general rule, never install software as root. As such, your user account would be the one with the darkcoin daemon running on it.
December 28, 2014, 06:22:14 PM
You have the root password?
su -
su -
Yes - I have the root password, but when I use it the terminal returns "Authentication failure" which is understandable because I disabled root login.
I suppose I could delete the server and start again but then I'd need to understand the interaction a bit better between the root user and the 'login' user. I think if I give the login user admin privileges ('sudo' privilages) when I create it then that would probably solve it. Maybe that's the difference between Tao's guide and the others - he doesn't give the login user 'sudo' privileges when he creates it but he seems to simply do everything under root when he needs to.
Then my question is, who's home should the ~/.darkcoin directory be created in - is it always the 'login user' ?
December 28, 2014, 06:16:51 PM
You have the root password?
su -
su -
December 28, 2014, 06:07:10 PM
Worst case scenario you reinstall the server. No big deal.
December 28, 2014, 06:02:03 PM
I tink I've shut myself out of my masternode server.
I disabled root login using sudo passwd -l root and then tried to switch to root user from my 'login user' account.
But it tells me that my login user isn't in the 'sudoers' file so I've lost root privileges and can't even shutdown.
Am I screwed ? Do I need to start again ?
This worked on Amazon EC2 (presumably because some 'switch' was used in the create 'login user' step). But it doesn't on Vulture.
How do I disable root login on Vulture without locking myself out ?
I disabled root login using sudo passwd -l root and then tried to switch to root user from my 'login user' account.
But it tells me that my login user isn't in the 'sudoers' file so I've lost root privileges and can't even shutdown.
Am I screwed ? Do I need to start again ?
This worked on Amazon EC2 (presumably because some 'switch' was used in the create 'login user' step). But it doesn't on Vulture.
How do I disable root login on Vulture without locking myself out ?
December 28, 2014, 03:57:00 PM
Next Litecoin dump incoming.
such a slow and painfull death of a coin... (we are talking about LTC).
You must be new in crypto
December 28, 2014, 03:37:48 PM
If you create a new wallet.dat, encrypt it, back it up, getnewaddress and send funds to it, does the back up of the wallet.dat also have the new address? Does getnewaddress actually create a new address or just assign one? Is that what the keypool size is?
You don't have to back it up after every new address generation.But you have to after importprivkey because it's a new privkey added to your wallet.
Doesn't each new generated public key have a new private key associated with it? So I you don't backup the wallet, you won't have the newly generated key pairs . Would be odd that it stored a bunch of keys just in case.
I did not know how that works either. Here it says "The keypool parameter just sets how many extra keys the client creates when it needs to create keys."
http://bitcoin.stackexchange.com/questions/770/what-does-keypool-1-do
the wiki does not give explicit information about this https://en.bitcoin.it/wiki/Key_pool
so YES, executing getnewaddress means you need a new backup
What you won't have is just addresses in your book.
Edit: You missed that post in your link:
"With keypool of 100 (the default) you could make 100 new addresses (via new transactions) and the backup would still be valid." – DeathAndTaxes Nov 5 '11
Satoshi https://bitcointalksearch.org/topic/key-pool-feature-for-safer-wallet-backup-1414
Jump to: