can anyone tell me if you can import the Kali tools to ubuntu 16.04 and if it makes sense to do it? I tried a couple tutorials that used Katoolin, but it was un successful

Ok, you're new, I get it. I was once too. But "it didn't work" doesn't help us help you. We need to know more about *why* it didn't work.

How To Ask Questions The Smart Way

You didn't provide a link to the tut you tried. I found this one:

How to Auto Install All Kali Linux Tools Using “Katoolin” on Debian/Ubuntu

It looks pretty simple and straight forward.

Where did it go wrong and how? What error messages did you get? Have you had any other problems w/ the system?

As to if there is any point: Maybe yes, maybe no. I can see where it would save a lot of headaches solving the problems of getting kali to run on metal. On the other hand you're going to loose at least some functionality b/c the devs @kali have done a bunch of tweaking; including a lot of kernel hacks. But you could always compile a custom kernel based on the UB16 default kernel and bake in those yummy kali changes!

But why UB16? I know it's ez/pz to use. But you do know that Shuttleworth has his nose up the butt crack of the Chinese gov / People's Party and that work in Kylin is now making its way back in to the upstream repo's and kernel of ubuntu as of 16, right?

Why not just bend over and grab both ankles while you're at it?

Now, I could see maybe doing this on deb8, after all that's what kali is built on. And while deb8 is not as fleshed out as UB16 it's a heck of alot easier to get on to metal than kali. But you'll still have the same functionality / kernel issues as above.

And you do realize that kali is not mean for everyday use, right? Starting w/ another OS and "grafting" kali on it will save some headaches for sure. But what's the point when it will cause functionality issues; especially when you start mixing repos.

You don't know which way is up yet and you want to start mixing repos? I hope you don't actually *need* the box for anything important b/c sooner or later it *will* go KaFnBoom, and you'll have no idea how to fix it. Then you'll get to learn about fun stuff, like dependency hell; which is always so much fun to play w/ from a live DVD on a box that won't boot.

My advise: Forget all the kewel 3117 h4xor toyz that won't let you rule the world any way and go get a nice little distro like deb8 and figure how to do things like build dummy meta-packages, install the tool chain and headers, compile a custom kernel and persistently load custom kernel modules and drivers before you try shoving a V8 in to Gremlin.

1 members found this post helpful.

Thank you Steven G, You have given me a lot to think through

Ubuntu should have all the same software available in its repositories as Kali. No reason to 'import' anything. In fact, if you really want to learn about security you should learn more about the underlying operating systems you use. Learning defensive security is more important if you are a novice than it is to learn offensive security. If you understand how to secure Linux, Unix, BSD, Windoze first , you will have less trouble learning how to break these operating systems.

What you need to be inquiring about is how to use the package manager in Ubuntu.

Actually no, the software in the UB and kali repos are not the same. A lot of the stuff in kali has been back ported from sid and is often *many* versions of ahead of what's in the UB repos. Plus there's a lot of custom work to the OS in general, the kernel in particular and a lot of packages in the kali repos. It *is not* just repackaged ubuntu (or deb8 for that matter) by any means.

The script in question temporarily switches the system over to kail repos and then back to ubuntu repos. That is a really good way to brick a system. Especially for a newbie who doesn't know what's *behind* the GUI front end of the "package manager", nor how to dig their way out of hell.

For that matter, just exactly which "package manager" are you suggesting the OP learn? The software center, update manager, synaptic, apt, aptitude or dpkg? I ask b/c I *have* played with swapping repos across distros on the deb tree, have had to dig my way out of hell and had to use *all* those tools to fix it, plus a lot of research and CLI work. I don't think advising someone new to jump in to that pool is good form; nor is misinforming them that kali and ubuntu might as well be the same thing.

I don't think I said that the software was the same version or that Ubuntu and Kali are exactly the same. I do see that what I wrote can be interpreted differently than intended. It is very frustrating how quickly the users of this forum rush in to say "you are wrong". You are attempting to educate me on topics I am well aware of. What I said was very simple, and maybe too simple. I will expand on it for clarification.

The software installed on Kali can be found in Ubuntu. Ubuntu has a massive software repository. It is also very simple to build missing software from source and to package it for later reuse. Anyone using pentest software should also have the ability to update said software to the version which is required for the job. When I say "update", I mean compiling from source. This includes feature patches, bug fixes, and security patches. I typically do not run software in its vanilla state for such tasks.

Which brings me to my main point (which you missed by the way). If I were going to break into a system, I am going to do so from my distribution of choice, of which I secured with a grsec patched LTS kernel, with Pax configured appropriately, a HIDS for my file system, and full disk encryption. To me defensively securing my system is always top priority before trying to make another system insecure. You simply do not know what you will encounter while accessing other networks and systems- whether it be with permission or not. The only exception to this is if you are testing with virtual machines on a closed network.

Kali is not designed as a secure system. It is a demonstration of a system strictly used for offensive security. It is meant for closed virtual networks, where any repercussions do not effect production. You are very likely to get yourself hacked if you run Kali without the proper security measures in place out in the wild.

1 members found this post helpful.

A) You expect new people to implicitly know this on the first day when you don't e'splain it?

2) You ain't as 3117 as you think you are if you're using grsec in your kernel. It has a lot of issues including, but not limited to: stability, compatibility, kernel management, being closed source, refusing to contribute back to upstream kernel development, they may well be in violation of the GPL and they refuse to submit to an outside security / code audit.

In my obviously, in your opinion, retarded opinion you're better off just compiling your own secure kernel w/o a bunch of crappy closed blobs slapped on it.

@) I wasn't trying to teach the OP how to be an 3117 h4xor. I was addressing their specific question and letting them know some basic info and potential pitfalls of that particular approach.

Now, when I built my home spun version of Kali on metal I fleshed it out and hardened it with packages from source, the deb8 repos and even aliened in some rpm's. But that is a whole dif ball o' wax.

I did not say that new Linux users should know those things. It was very clear what I said. If you are unable to read text on a page, it is pointless to discuss further. I am just trying to help the OP understand that there are steps to take before going out and using software on any distribution that is used to penetration test. My choice in software doesn't make me stupid or retarded. In fact I think insulting the users of this forum infringes upon rule #1 of LQ, and possibly rule #3. This forum is a community and people like you ruin it. The only thing your responses are doing is detouring new Linux users away from using Linux.

Where does it say that I want to teach the OP to hack? The fact that you have turned this post into an argument is ridiculous. Anyway, I do not care for your opinion at this point...

...because of this.

OK, now I am insulting you:

If your reading comprehension were just a little better you'd be able to read that crack as: "You obviously think my opinion is retard, so why am I bothering to try you educate you any way?"

And I'm sorry that you don't have the skill level necessary to re-spin kali for yourself and harden your kernel w/o slapping a bunch of crappy closed blobs on it.

I would suggest that you acquire these skills before trying to help new people with things that you obviously don't fully understand.

Moderator note:

Dear Steven_G,
You may disagree with other member opinions, but do it with respect. Insulting other members isn't tolerated at LQ.

Duly noted.

However, since I was accused of it but didn't do it before I figured I might as well go ahead and do what I had been accused of.

It won't happen again.

A thousand pardons.