andreaso
Joined 15 years ago
Karma
76
Submissions
23
Member since
Sep 28
Recent submissions
Comment · 1 month ago
Comment · 9 years ago
That sshd only supports the chacha20-poly1305 cipher.
Perfectly fine with that, since I'm the only one logging into that server.
Comment · 9 years ago
It appear to have problems with newer chiphers.
sshd[28670]: fatal: Unable to negotiate with 40.112.150.31 port 47286: no matching cipher found. Their offer: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-ctr,3des-cbc,twofish256-ctr,twofish192-ctr,twofish128-ctr,twofish256-cbc,twofish192-cbc,twofish128-cbc,twofish-cbc [preauth]
Comment · 10 years ago
Does it really matter that much what distro it ships with? As long as the laptop ships with any distro preinstalled that hardware tend to be properly supported by the Linux kernel, allowing you to feel safe about installing any other (up-to-date) distro.
Comment · 10 years ago
I'd imagine there are people who consider the article relevant based on its author.
https://en.wikipedia.org/wiki/Adam_Leventhal_%28programmer%2...
Comment · 11 years ago
To be fair, at least the Tor Project itself makes a rather serious effort to be upfront with its own limitations, etc.
For example, when you use the (recommended) Tor Browser Bundle the start page contains a window containing the following headsup
"Tor is NOT all you need to browse anonymously! You may need to change some of your browsing habits to ensure your identity stays safe."
As well as a link to https://www.torproject.org/download/download.html.en#warning.
That same warning is also present on the main download page: https://www.torproject.org/download/download-easy.html.en
Comment · 12 years ago
Well, if you want you can always manually download and verify the the packages.
1) Find list of applicable binary packages, for example by taking a look at https://packages.debian.org/source/wheezy/apt
2) Download http://security.debian.org/dists/wheezy/updates/InRelease, and verify the gpg signature against the archive signing key, found in /etc/apt/trusted.gpg alt. in /etc/apt/trusted.gpg.d/*.gpg
3) Download http://security.debian.org/dists/wheezy/updates/main/binary-..., and verify that its sha256 sum matches what you have in your previously downloaded InRelease file.
4 Inside the downloaded Packages.bz2 you'll find the relative paths as well as the sha256 sums of the packages you want to download.
If nothing else this is a good exercise to see how the different pieces fit together.
Comment · 12 years ago
Yepp, and there is already an existing tool, which currently supports GitHub as well as Launchpad.
http://manpages.ubuntu.com/manpages/trusty/en/man1/ssh-impor... https://launchpad.net/ssh-import-id
Comment · 12 years ago
Well, despite its imperfections, how does DNSSEC worsen security compared to regular DNS? Besides, it's not like the use of DNSSEC prevent you from continuing to also rely on additional measures; such as good old fashions CAs, or something better.
Comment · 12 years ago
Yeah, I'm getting that same premium experience.
Appear to also hit Google Apps as well as any AppeEngine hosted site.
Comment · 12 years ago
Well, FreeBSD 9.0 merged those patches into its OpenSSH. Perhaps that was what was floating in the back of your mind?
Comment · 13 years ago
A bit unhappy about Indiegogo, insisting on "Shipping Address Line Two can't be blank"; when my regular postal address really is fully covered by Name, Country, Address Line 1, City and ZIP Code.
Sure, I could probably fill in some kind of apartment number or so. Yet, it's not something I usually have on in my postal address, and it's definitely not something getting a line of its own.
Also, that seemingly broken requirement bugs me.
Comment · 13 years ago
You know, IPv6...
I'm getting a false "Your email has been received and it doesn't leak your IP", due to the fact that the web site is only available using IPv4 while I'm connecting to my SMTP server over IPv6. As long as the website only captures IPv4 addresses it really might need to display an inconclusive result in the presence of IPv6 received headers.
Oh, and when the web site do become IPv6 reachable you probably will want to make an explicit attempt to also catch a potential IPv4 address, in the case situation above is the reverse.
Comment · 13 years ago
I have a clavid.com openid delegated using my own domain...
Comment · 13 years ago
While I mostly agree I also think that having some legal/jurisdictional protection is a good thing. If nothing else for the case where there turn out to be an exploitable weakness in the client side encryption you are using.
Looks like it's the glue records that point to the actual server?