text
stringlengths
0
1.49k
[508.66 --> 512.72] And now this is agnostic to what you use for your vendoring tool, right?
[513.30 --> 513.92] Yeah, correct.
[514.08 --> 516.16] You can vendor with whatever you want.
[516.24 --> 522.74] A few tools will freak out if you are not in GoPath, which is kind of legitimate because
[522.74 --> 525.82] vendoring doesn't even turn on outside GoPath.
[525.82 --> 531.96] But if you can get them to actually do their job and vendor stuff, any tool that you use
[531.96 --> 533.04] for vendoring will do.
[533.54 --> 536.84] I patched GVT so that it doesn't complain if there's a make file.
[537.60 --> 540.06] So that's how I sold it in GVT.
[540.64 --> 541.10] Nice.
[541.80 --> 544.90] And now you actually work on all kinds of cool stuff.
[545.24 --> 548.94] I've been following you for a long time because of all the security stuff you do.
[549.40 --> 553.48] One of my favorite things you did was the WhoAmI SSH server.
[553.48 --> 555.30] I still love this.
[555.52 --> 556.22] It's creepy.
[557.06 --> 562.86] Yeah, you can understand how SSH works and how keys are exchanged, but it doesn't really
[562.86 --> 565.08] connect how you could leverage that.
[565.40 --> 571.72] Actually, for anybody who's not familiar with it, do an SSH to WhoAmI.philippo.io.
[572.38 --> 573.52] It's a lot of fun.
[573.62 --> 575.62] Do you want to tell everybody kind of what it is and explain?
[575.62 --> 580.60] I should tail the logs and say hi to people, but that would be even more creepy.
[582.52 --> 589.74] So, yeah, WhoAmI is this little demo that came out because my flatmate, who deserves
[589.74 --> 594.98] a lot of the credit, had dumped all the public SSH keys of GitHub.
[594.98 --> 600.32] I don't know if you might not realize, but if you go to github.com slash your username
[600.32 --> 603.56] dot keys, it will show you your SSH keys.
[603.80 --> 605.68] That's super handy for a number of reasons.
[605.68 --> 609.20] Like I want to give this person access to my box or something like that.
[609.64 --> 616.00] But, you know, you can just scrape the whole, not even scrape, just use the GitHub API to
[616.00 --> 618.80] get a list of all users, download all the keys.
[618.80 --> 626.56] And now you have a pretty good idea of a huge chunk of the SSH keys to whom they belong.
[627.36 --> 631.52] And at the same time, I was like studying the SSH protocol and trying to figure out a
[631.52 --> 633.18] bit of the internals and such.
[633.48 --> 640.62] And I realized that the default behavior is just to send preemptively the public keys you're
[640.62 --> 641.60] willing to use.
[641.98 --> 645.20] Then the server responds, oh, yes, I like this one.
[645.20 --> 651.88] So if the server responds that, then you make a signature with that key to log in.
[652.36 --> 656.08] But if the server refuses them all, it will still see them all.
[656.56 --> 664.02] So I built this little tool with the golang.org slash x slash SSH package that would ask you
[664.02 --> 671.70] to use your public keys, refuse them all, but like log them, then ask you to do keyboard
[671.70 --> 676.90] interactive login, which is a weird thing that I could just like make happen automatically.
[677.18 --> 679.44] So log you in, in any case.
[679.92 --> 684.24] And then if I found you in the database, I would tell you your name and surname and GitHub
[684.24 --> 687.40] account because I cross-referenced it to the database.
[688.26 --> 695.66] And once you explain it is kind of trivial, but like the surprise, the impact is pretty strong.
[695.66 --> 700.50] So I ran it on my machine and it didn't find my GitHub public key.
[700.68 --> 706.98] I'm wondering if it's because I have multiple ones and you grabbed one that wasn't active?
[707.58 --> 713.26] So the way the SSH protocol works is when you do public key authentication is it will pass
[713.26 --> 714.40] all of your public keys.
[714.62 --> 721.42] So anything that's in your .SSH directory, you'll see like the ID underscore RSA.pubs
[721.42 --> 722.78] and things like that.
[723.36 --> 726.86] It will pass that, which contains your email address in it.
[727.26 --> 727.70] Oh, yeah.
[727.86 --> 730.64] I mean, there's that, but I don't even use that.
[730.88 --> 733.66] I use the matching of the actual public key.
[733.80 --> 734.38] Oh, that's right.
[734.46 --> 734.62] Yeah.
[734.62 --> 736.48] Because you have a list of the actual keys.
[736.86 --> 737.00] Yeah.
[737.30 --> 739.28] So I'm trying to figure out why I didn't find mine.
[739.62 --> 742.00] Is that key added to your GitHub account?
[742.52 --> 745.30] I'm using this computer to log into push to GitHub.
[745.74 --> 746.10] Interesting.
[746.56 --> 746.74] Yeah.
[746.82 --> 749.88] So what's happening is probably that the database is out of date.
[750.04 --> 750.32] Yeah.
[750.32 --> 754.22] We should like wait for Ben to get home and ask him that, I think.
[756.50 --> 757.06] Call him.
[757.08 --> 759.64] Sorry, our DBA isn't available right now.
[760.18 --> 761.10] Phone a friend.
[762.76 --> 765.56] Yeah, I want to use the help from home.
[767.72 --> 768.12] Nice.
[768.20 --> 771.02] I just added a function to my bash functions directory.
[771.20 --> 776.74] So now I could just type hello go for any directory and it will use wget to get the hello go for make
[776.74 --> 778.54] file and add it to the current directory.
[778.70 --> 779.96] I can't wait to go try that out.
[779.96 --> 780.32] Nice.
[780.54 --> 780.90] Nice.
[781.32 --> 782.26] All about some aliases.
[782.78 --> 782.92] Yeah.
[782.92 --> 787.12] The cool thing about that who's there thing is, is it really makes you connect with how
[787.12 --> 789.02] much information leakage there is.
[789.28 --> 793.92] Like you don't really consider that when you try to SSH a server that you're leaking information
[793.92 --> 800.48] that you, you could be giving away, say, email addresses or, or those keys could be used
[800.48 --> 803.16] to, you know, match you against other databases.
[803.16 --> 804.54] So really interesting.
[804.54 --> 804.94] Yeah.
[804.94 --> 805.26] Yeah.
[805.26 --> 810.70] I didn't even go full creep on it because from the GitHub account, you can probably jump
[810.70 --> 817.74] to the key base account if you have key base and, or like use the links you have in your bio.
[817.74 --> 820.96] And from there, jump to your Facebook or your Twitter.
[820.96 --> 826.12] And from there, jump to your bio, maybe your home address, maybe your phone number.
[826.78 --> 827.80] That would have been nice.
[827.90 --> 832.26] Like, hello, you're trying to association to a server where you're going to get a phone call in a minute.
[832.26 --> 833.32] Oh yeah.
[833.40 --> 837.08] I mean, you really could go full on creeper because you could basically take like the domain
[837.08 --> 841.26] from their, their email address and then start doing who is, is on it.
[841.36 --> 843.54] And yeah, you could get all kinds of information.
[844.04 --> 844.20] Yep.
[844.60 --> 846.46] So what other things are you working on?
[846.54 --> 848.52] I know you're doing some TLS stuff as well.