text
stringlengths
0
1.17k
[2221.84 --> 2227.14] this project um well i mean i was like thinking like well uh you know ruby is a really great
[2227.14 --> 2232.18] language for doing dsls uh there's already like you know you could think of rails as kind of a
[2232.18 --> 2236.74] dsl framework uh for doing web development because they kind of wrap everything up and
[2236.74 --> 2242.40] nice helper methods and so it like it abstracts away a lot of the complexities like i'm talking
[2242.40 --> 2249.14] like rails 2 old school um now it's really complex these days but uh so i kind of thought like
[2249.14 --> 2253.04] well hey this ruby language might be pretty useful uh because like i was looking at the
[2253.04 --> 2258.80] documentation for instance they have like a telnet module and it's really nice we can use the blocks
[2258.80 --> 2263.98] to automatically set up the telnet session handle it and tear it down so i was like wow this can
[2263.98 --> 2269.14] actually be pretty useful for writing exploits because exploits really aren't that complex code
[2269.14 --> 2275.90] wise and you could also then write a lot of the helper methods and make everything basically one
[2275.90 --> 2281.34] basically doable in one line of code where you just string together the helper methods
[2281.34 --> 2287.22] and so that was kind of my um my project with ronin was to create an environments
[2287.22 --> 2292.64] uh with kind of like active support type library called run support that provided all the helper
[2292.64 --> 2297.64] methods which are called convenience methods uh for various things that like security research need to
[2297.64 --> 2304.34] like all the time and then provide kind of a main kind of console environments and then a system for
[2304.34 --> 2310.04] installing repositories of other people's code um because you know back back within people are
[2310.04 --> 2316.84] still using ruby gems dot ruby forge dot org to distribute so it's a lot easier um for your kind
[2316.84 --> 2322.14] of average security researcher who isn't really like a top level developer they're that's not what
[2322.14 --> 2327.22] they're after they're like trying to do research and break things and find cool vulnerabilities and so
[2327.22 --> 2332.12] it was kind of a lot easier in my mind it's like basically just have a repository system they can give
[2332.12 --> 2338.80] a url and it'll pull down some svn or a git or whatever um directory of their code and
[2338.80 --> 2344.08] pull it all together but yeah it's kind of one of my big one of my first big projects and that
[2344.08 --> 2351.38] spawned a lot of different other libraries and gems and then because like a lot of code got pulled out of
[2351.38 --> 2357.34] it as it kind of matured um so a lot of useful code kind of got split out of that so and i was kind of
[2357.34 --> 2364.36] following the uh the model that data mapper uh followed that's basically they split everything up into
[2364.36 --> 2371.62] uh smaller amounts smaller libraries over time and so i was kind of like doing that but um
[2371.62 --> 2377.36] yeah so i kind of got caught up in work and so i like kind of like put ron more to the to the side
[2377.36 --> 2382.04] but now i'm sort of like thinking about how things have changed and definitely want to get back on the
[2382.04 --> 2388.98] project and simplify some various things so you do plan to get back into ronin that's oh yeah yeah
[2388.98 --> 2394.46] gotcha there's a lot of unfinished code in there gotcha so this is an interesting i i think this is
[2394.46 --> 2399.06] interesting to me because you were kind of doing security research with ruby four years ago and
[2399.06 --> 2407.10] the amount that ruby has changed in the last four years or you know in the last x years uh
[2407.10 --> 2411.86] i mean you've had to keep up with a lot of change so what has the process been like maintained i think
[2411.86 --> 2417.28] this might be one of the oldest uh actual like uh projects that is still maintained that we've
[2417.28 --> 2422.94] actually had on the show what's that been like oh yeah well i mean there's those periods of rapid
[2422.94 --> 2428.12] growth in the ruby community where we had things like uh you know we switched uh we switched
[2428.12 --> 2433.64] jeweler and then we switched off jeweler and then we had bundler and then we kind of like
[2433.64 --> 2438.14] there's all these kind of evolution of tools and so it's kind of really difficult to keep up and we
[2438.14 --> 2444.20] you know we went we transitioned from ruby forge to ruby gems uh then rvm came along so it's kind of
[2444.20 --> 2449.92] difficult to keep up all these tools and actually found myself kind of like gradually moving away from
[2449.92 --> 2456.32] the tools or not just like it seemed like when any of these tools came out we everyone just sort of
[2456.32 --> 2461.96] like we must use this everywhere possible all the time irregardless and i kind of found myself that
[2461.96 --> 2468.72] it's really not that necessary for instance if your library has like one or two dependencies and
[2468.72 --> 2474.10] they're probably installed anyways like the json gem or rake you probably don't you don't need bundler
[2474.10 --> 2481.68] and um so yeah i'm like and also kind of developing these tools that these libraries they were kind of
[2481.68 --> 2486.40] my like personal playground and so i did kind of like develop tools based out of that because i got
[2486.40 --> 2493.96] tired of like having to always edit the read me that was generated by jeweler or or by hoe or by uh
[2493.96 --> 2498.96] bundler i just wanted to like project set up automatically with like rspec and all that stuff
[2498.96 --> 2506.82] and so i kind of wrote like a uh or which is like a project skeletoning tool and says it has been a bumpy
[2506.82 --> 2512.54] road and it's especially annoying when there's like issues with ruby upstream um like kind of the
[2512.54 --> 2519.32] major like whatever like open ssl would break things or um but at the same time it has been nice where we
[2519.32 --> 2524.44] did develop tools to deal with that's where i for instance like a long time i just always recommend
[2524.44 --> 2531.18] people to install rvm first and then you know before installing ronin and like install the latest version
[2531.18 --> 2537.32] but at the same time i kind of felt like you know we were moving a little too quickly and maybe it
[2537.32 --> 2542.48] would have been a little better to sit back and kind of like reevaluate what what our actual needs
[2542.48 --> 2549.16] are because like for instance the same thing with how um rbm kind of um inherits a lot of the features
[2549.16 --> 2556.96] and like uh ways of doing things from rvm you kind of also saw that in bundler about how bundler
[2556.96 --> 2564.76] basically also developed its own little static project generation tool and which like was basically
[2564.76 --> 2571.84] constantly being changed and updated and because it's really hard to get get rights first um because
[2571.84 --> 2578.90] everyone has like little nitpicky uh changes to like how they want projects generated and um or it also
[2578.90 --> 2584.28] has like you know it embeds their own release tasks which are kind of like crummy they don't they
[2584.28 --> 2590.40] don't use proper rake file tasks and so you know like always rebuild your gem irregardlessly of even
[2590.40 --> 2595.62] if no files have changed so i kind of felt like uh you know maybe a little better to actually like
[2595.62 --> 2601.06] slow down and kind of like take stock of things uh so i'm just constantly racing around trying to
[2601.06 --> 2610.00] release versions all the time yeah so one thing i wanted to to kind of bring up the we forgot to talk
[2610.00 --> 2614.50] about this before actually um with ch gems and and sorry to kind of do a huge context switch here
[2614.50 --> 2620.70] uh we actually didn't talk about ch gems can you just give me a just uh kind of introduce what ch
[2620.70 --> 2626.30] gems is real quick and i have a question about it for you so ch gems was sort of my attempt to kind
[2626.30 --> 2631.96] of rethink gem sets because one of the kind of assumptions that go along with gem sets is they're
[2631.96 --> 2639.00] always named and they always are stored in your dot gem directory wherever that is and i kind of want
[2639.00 --> 2644.56] and then also they had to be implicitly uh like auto switched so which kind of did make sense
[2644.56 --> 2651.94] because the majority of the time like you would have this like rvm gem set file and it would have
[2651.94 --> 2657.08] a name in it and would use that gem set when you cd'd into the directory it would then activate the
[2657.08 --> 2662.34] gem set and i kind of thought that this was like first of all like uh it didn't feel too comfortable
[2662.34 --> 2667.08] of having like this automatic feature and i didn't really agree if always having the gem sets in
[2667.08 --> 2672.90] and your home directory is like why not just put the gem set in the actual project directory
[2672.90 --> 2680.44] in the same way that uh you know you can do uh bundler install and put everything in vendor gems
[2680.44 --> 2686.22] and then i kind of decide well let's take a different approach because there's like apparently also a lot
[2686.22 --> 2692.52] of people wrote their own kind of gem set replacement scripts there's like oh my gems there's is it rev
[2692.52 --> 2700.16] that's one version and uh also it was a gs gem switcher and i basically just wanted to make
[2700.16 --> 2705.08] something that instead of you actually have to like enter into a gem set and then leave because
[2705.08 --> 2709.90] i always would find myself when using rvm gem sets forgetting that i was still in that gem set
[2709.90 --> 2715.28] and being like oh hey that's that's why half my gems are missing yeah then you install a bunch of
[2715.28 --> 2719.20] gems to the wrong gem set and get all pissed off and you have to clean it up right and like we're just
[2719.20 --> 2723.60] like you forget about it you've made it for a project that like you know you wanted to make a
[2723.60 --> 2728.42] couple line fixes to this like huge project that had zillions of dependencies and so you want to like
[2728.42 --> 2733.94] isolate it some gem gem set and then you forget about it and like you don't remember it when you're
[2733.94 --> 2739.18] like going around cleaning up your home directory wondering why you don't have any space left um
[2739.18 --> 2746.22] yeah so i kind of like took the approach of uh ch root where you can uh basically explicitly
[2746.22 --> 2752.94] enter into a project and then that starts a or like a system image and then it starts a subshell
[2752.94 --> 2757.50] within that system directory and makes that the current route and it's kind of nice because you
[2757.50 --> 2763.44] can basically exit out of the shell and you go back to your previous uh environments your previous
[2763.44 --> 2769.04] system so i kind of felt that that was a really good model um basically explicitly like go into a
[2769.04 --> 2775.76] project and then leave um but yeah there's actually some problems in rows with that and um
[2775.76 --> 2782.88] because the way that ch ruby auto switching was expected to work uh people who use tmux for instance
[2782.88 --> 2791.20] when they opened a uh split pane or another split terminal it didn't properly initialize or inherit the um
[2791.20 --> 2798.12] the shell environments from the other terminal and so basically a lot of ch ruby i mean uh tmux users
[2798.12 --> 2809.16] um requested that ch ruby always auto uh set the ruby version on on new subshells so uh so i had to
[2809.16 --> 2815.96] make that change and that kind of ended up uh conflicting with ch gems because ch gems uh spawns a subshell
[2815.96 --> 2823.72] and so there's kind of this weird kind of like race condition where um ch gems basically sets the gem home and