 Show Posts
|
|
Pages: [1] 2 3 »
|
|
sending spam emails is certainly not going to make me sign up
|
|
|
|
Alexz: Wouldn't it be easier to just use the "git shortlog" command? It can show the commit count per author (see my previous post). The only problem is that the same author can appear under different names (e.g. in the output above: s_nakamoto, Satoshi Nakamoto and --author=Satoshi Nakamoto (which was some command line mistake im sure  )). The .mailmap feature might be able to solve this though. See bottom of http://www.kernel.org/pub/software/scm/git/docs/git-shortlog.html |
|
|
|
output of "git shortlog --summary --numbered --no-merges" 245 s_nakamoto
92 Gavin Andresen
56 Matt Corallo
35 Jeff Garzik
32 Pieter Wuille
26 Satoshi Nakamoto
26 sirius-m
19 gavinandresen
17 Giel van Schijndel
12 tcatm
8 --author=Satoshi Nakamoto
8 Jordan Lewis
7 Han Lin Yap
6 Vegard Nossum
5 Chris Moore
5 Doug Huff
5 Matt Giuca
4 Chris
4 Dev Random
4 Eric Hosmer
4 Jay Weisskopf
4 John Maguire
4 Wladimir J. van der Laan
4 devrandom
3 Michael Bemmerl
3 Venkatesh Srinivas
2 Carlo Alberto Ferraris
2 Daniel Folkinshteyn
2 David FRANCOIS
2 Dawid Spiechowicz
2 Marius Hanne
2 Ricardo M. Correia
2 Stéphane Gimenez
2 Witchspace
1 Abraham Jewowich
1 Amir Yalon
1 Anonymous
1 Blitzboom
1 Carlos Pizarro
1 Dan Helfman
1 Dan Loewenherz
1 Daniel Holbert
1 Danube
1 Dean Lee
1 Dylan Noblesmith
1 Eric Swanson
1 Fabian H jr.
1 Federico Faggiano
1 Forrest Voight
1 HostFat
1 Jakob Kramer
1 James Burkle
1 Jaromil
1 Jeroenz0r
1 JoelKatz
1 Joerie de Gram
1 Johannes Henninger
1 Luke Dashjr
1 Michal Zima
1 Nils Schneider
1 Patrick Varilly
1 Santiago M. Mola
1 Shane Wegner
1 Sven Slootweg
1 ariel
1 dabaopku
1 gjs278
1 laszloh
1 m0ray
1 mewantsbitcoins
1 ojab
1 ovdeathiam
1 sandos
1 xHire
|
|
|
|
Yours is just a fundamentalist party line, that seems to refuse that 95% of the talking being done about Bitcoin is because it has a peg to the dollar, and as such has a baseline store of value that becomes more reliable the more people buy it for the dollars you're so against.
But bitcoin ISN'T pegged to the dollar. Or any other currency for that matter. |
|
|
|
That makes no sense.
I see how it wouldn't make sense for a DUMBASS |
|
|
|
|
regardless of what actually happened, if you got hacked by the "dumbest hacker", doesnt that technically make you even dumber than the hacker?
|
|
|
|
|
it does, also make sure that the .ssh directory is also only read and writeable by "cyper"
|
|
|
|
duh, you did not listen to what I said, the permissions and the owner are completely wrong run the following sudo chown cyper:cyper authorized_keys
chmod 600 authorized_keys |
|
|
|
1 - So then the keys will be in different formats? Why would that work?
2 - I've tried that function before when using different tutorial, but it didn't work.
3 - I think I'm doing everything right, but to no avail.
1 - Why wouldnt it? The keys are only stored in different formats, putty needs the putty format, openssh needs the openssh format. 3 - If you would be doing everything right it would be working by now. Post a ls -l output of your .ssh directory. |
|
|
|
1 - Do I need to convert the private key (which stays on the Windows machine) to OPENSSH format?
3 - What command do I use on the Ubuntu machine to convert the public key generated by PuttyGen into OpenSSH format?
4 - I can do it with the GUI, right? As shown in the screenshot above. I make sure it's a single line.
Like I said I've tried 2 or 3 different tutorials and I only get Server refused our key.
1) No, you dont. 3) I dunno, but a quick google search tells me that the puttygen GUI has a conversion function. also note that you can do this step on your client or host machine, it doesnt matter. 4) You can edit the authorized_keys file with any editor you want, just make sure it has the right permissions |
|
|
|
Let me see if I understand correctly - First I create a private key under Windows using Puttygen and after I copy this private key to the Ubuntu machine I use again Puttygen to generate the private and public keys out of the private keys I created earlier with PuttyGen under Windows.
Are you sure that is the way, cause that's how you explained it. The program for generating keys under windows is Puttygen and it can create either a private or public keys or both.
You NEVER move a private key to another machine. You also generate keys only ONCE, and only on CLIENT machine. 1) Create a KEY PAIR using putty on your client machine 2) Copy the PUBLIC KEY to the Ubuntu machine 3) Convert the PUBLIC KEY on the Ubuntu machine into OPENSSH FORMAT 4) Append the OPENSSH PUBLIC KEY to the authorized_keys file in the ~/.ssh/ directory Step 1) is done on the client machine, step 2) is sorta inbetween and 3) and 4) are done on the host machine. |
|
|
|
First: After you've created your putty key under Windows (puttykey.ppk), copy it to your Ubuntu server. We'll assume you have it in your home directory on your Ubuntu server which is ~/. So, that file is now ~/puttykey.ppk On your Ubuntu box, run a terminal (or SSH in from your Windows box) and: sudo apt-get install putty
When that's done, you now have putty on Ubuntu. Next do: puttygen ~/puttykey.ppk -L > ~/.ssh/id_rsa.pub
If you're not familiar with Unix/Linux then you won't realize this, but the key output is being redirected to a file named "id_rsa.pub" in the .ssh directory in your home directory on the Ubuntu server. Finally, create the private key on Ubuntu using: puttygen ~/puttykey.ppk -O private-openssh -o ~/.ssh/id_rsa
Now you should be able to do public key logins to Ubuntu. You MAY still have an issue due to permissions, so I'd recommend also doing: address
chmod 700 .ssh
chmod 600 .ssh/id_rsa*
Good luck. I'm pretty sure that is completely wrong since the id_rsa* files .ssh are the public/private key files of THAT machine, and do not specify which public key is allowed to connect. They would only be used if you ssh'd from that machine to somewhere else. Furthermore there should be no need to create ANY keys whatsoever on the host machine. Rather, you want to append your public key you created with putty on your client machine to the authorized_keys file in the ~/.ssh directory on the host machine. If that file does not exist create it and then run "chmod 600 authorized_keys". Depending on the format putty uses you might have to convert it to the openssh format first. There should be one key per line in the authorized_keys file, e.g. it should look similar to this: ssh-rsa AAA[lots of characters]== bla@foo So basically: append the .pub file you created on the client machine to the authorized_keys file of the host machine |
|
|
|
|
make sure the file permissions of authorized_keys is set to 600 and owned by the user you are using to connect or openssh will refuse to use it.
|
|
|
|
SSL is worthless. The Feds (and the Fed) have backdoors in most modern SSL software that allows them access to it, and I am certain that some hackers out there probably have access to it as well.
Never, ever type your Social Security number, Credit/Debit card information, or real name into any website - only use them all at the DMV and retail stores.
This is total bullshit. That being said, there is no need for a backdoor anyway, when the Fed can just get issued a VALID cert for any domain. Look through the CA lists that come as fully trusted with every browser download and tell me if you really trust everyone in there. At least with a self-signed certificate there is no way for someone to pose as your website. Like it has already been said numerous times in this thread, the browser warning for a self-signed certificate really needs to change. A big red warning that takes several clicks to get past should only be displayed if a PREVIOUSLY ACCEPTED certificate changes. There is a Firefox extension that sort of does that already. |
|
|
|
John Smith is working on a Qt interface here http://forum.bitcoin.org/index.php?topic=15276.0However, I am strongly opposed to adding a USD column because that would make the client depend on an exchange and give the impression that BTC is tied to the dollar. |
|
|
|
Some people want to just spend and receive coins without even seeing address strings or wallet details. Others will be power users, and want more fine-grained control over their wallet(s), keys, encryptions, and super-security techniques. And there's a million shades of gray in between. I don't think all this can be achieve with one client.
I think a nice future addition to the Satoshi client would be some kind of EXPERT MODE that can be turned on in the options (disabled by default) that enables all that (and possibly more). |
|
|
|
|
