Live data from Hacker News

Kali Linux 2020.3

kali.org

71–80 of 102 posts

Re: Kali Linux 2020.3

#71
post #48

I always thought Kali wasn't really for daily use. Not a vehicle for every day driving around town, more like a secondary vehicle you only use for work. HiDPI, tool icons, and gnome themes make it seem otherwise. Sure, these things are nice whether you're using it for work or play, but I wonder. Is anybody running kali as their daily driver?

I can’t find the article and relevant study right now, but people actually perform better when they are using aesthetically pleasing gear. That would include software.

Re: Kali Linux 2020.3

#72

Earlier quoted context omitted.

People who don't use Kali comment on whether move from one shell to another was right for the Kali users. This drive by commenting is sadly omnipresent in the open source world. OpenBSD uses CVS? They should use git. XServer? Why not Wayland? Oh, libsdl is using Mercurial, but they should totally use git. And on, and on.

Drive by comments are typically from people who want to sound like an expert.

I find it extremely amusing that your comment has been sufficiently downvoted that it's grey...

Re: Kali Linux 2020.3

#73

I think the move of Kali Linux from bash to zsh is sane. I sometimes have to use the default shell of Linux distribution, especially on servers, and my main pain points with bash are: - The history is editable by default. If I move to a previous history line and change it, the old line disappears. Hitting Ctrl-c will remove it from the history. - If I use simultaneous shells (screen, tmux, or several ssh connections)…

At the end of the day, whatever shell best suits you basically boils down to usage, habits and how much willing you are to tweak it.

Re: Kali Linux 2020.3

#74
post #31

I think the move of Kali Linux from bash to zsh is sane. I sometimes have to use the default shell of Linux distribution, especially on servers, and my main pain points with bash are: - The history is editable by default. If I move to a previous history line and change it, the old line disappears. Hitting Ctrl-c will remove it from the history. - If I use simultaneous shells (screen, tmux, or several ssh connections)…

> - The history is editable by default. If I move to a previous history line and change it, the old line disappears. Press M-r to revert back to the original command. > - No way to set a command aside. E.g. if I realise while typing that I'm not in the right directory, `git clone cd src `. Press M-# to comment out the current command and go to a new prompt, then up to get the commented command back, and M-3 M-# to un…

Oh look! Magic!

I think if bash had some interactive help with this magic when it appears then it would be a lot more helpful and a lot less magical.

Re: Kali Linux 2020.3

#75
post #69

Kali Linux still exists? I thought after it was used in so many more or less good films and series it is not cool any more. :D

It's very lively and actually the cancer of certain parts of the internet (like the subreddit dedicated to Virtualbox).

i just took a look. wow, the number of people who have just discovered fire over there.

Re: Kali Linux 2020.3

#76
Can anyone recommend training for offensive security and/or Kali Linux pentesting?

I've been wanting to explore that branch for a long time, I'd really appreciate some great resources for an engineer with no pentesting experience.

Re: Kali Linux 2020.3

#77

Aren't the people who know and understand the tools they use, the same people who can install security utilities on any distro? What is the purpose of this distro in regards to that?

It's just another type of test harness.

It's Debian Live, so you can extend or customize it to suit a particular need. That it is ready to run and leaves no trace adds a lot of value.

You may not win a bounty from a vendor, but it's pretty trivial to take their app, add it to an image and expose potential vectors.

Your own PIR may benefit from the forensics tools (without the lead time of getting them working).

It doesn't deliver any 'security' on its own.

Re: Kali Linux 2020.3

#78

Can anyone recommend training for offensive security and/or Kali Linux pentesting? I've been wanting to explore that branch for a long time, I'd really appreciate some great resources for an engineer with no pentesting experience.

This is a copy/paste of one my comments from a different thread.

Disclaimer: I'm not particularly good at this, so whatever comments I make are well intentioned but may be of varying accuracy.

...

Online sources:

* https://hackthissite.org Wargaming site. Plenty of challenges to practice, but some are a bit outdated.

* OWASP.org is a good place to find info. If you look something up, there's a good chance you will find it here.

* https://owasp.org/www-project-web-security-testing-guide/ Thanks to redis_mic for this one.

* https://overthewire.org Similar to HTS, but you don't need an account. The subject matter covered is also slightly different.

* https://0x00sec.org/ A forum dedicated to security. There's a lot of script kiddies, but also some gold.

* https://www.hackerone.com/ What better way to learn then practice on live targets? That being said, I would do some of the others first.

...

I do a lot of learning through reading, so books:

* Network Security Assessment by Chris McNab. I have second edition, which is a good and instructive read, but quite outdated.

* Real-World Bug Hunting by Peter Yaworski. Web security 101. Good read, and fairly useful.

* Advanced Penetration Testing by Wil Allsop. Outdated, but interesting. You will never use flash again after reading this.

* Social Engineering, The Science of Human Hacking by Christopher Hadnagy. This is a very interesting read. Also, one of the few that can't go out of date.

...

This should be enough to get you started. There's a couple more books I can think of, but they tend to be more specialized into certain fields of security and less approachable/generally applicable. If you want these recommendations as well, feel free to email me, my email's in my bio.

Re: Kali Linux 2020.3

#79
post #31

Earlier quoted context omitted.

> - The history is editable by default. If I move to a previous history line and change it, the old line disappears. Press M-r to revert back to the original command. > - No way to set a command aside. E.g. if I realise while typing that I'm not in the right directory, `git clone cd src `. Press M-# to comment out the current command and go to a new prompt, then up to get the commented command back, and M-3 M-# to un…

Oh look! Magic! I think if bash had some interactive help with this magic when it appears then it would be a lot more helpful and a lot less magical.

I don't think bash really fits the type of program to have interactive tutorials. If you are serious about your command-line-fu its worth giving the manual a good read.

bind -P | grep '\\e'

https://www.gnu.org/software/bash/manual/

My favorite by far is '\e.' or 'M-.' which inserts the last arg from your previous command. Discovering this led me down the bash rabbit-hole of finding new commands, creating my own and really enjoying the bash shell. Did you know you can execute arbitrary code as one of these commands? I had one that ran 'docker ps' so I could list my containers in the middle of typing a command.

Re: Kali Linux 2020.3

#80

Earlier quoted context omitted.

Fun fact: That's a legacy openstep thing. I was using an x86 version of openstep in a VM just for fun a few months back and it had a 1994 copy of zsh on it. I also remember using it on OS X server 1.0 in around 1999. I have an actual nextstation in my parents garage. I wonder if it's on that...

OS X used tcsh as the default shell way back. Later it used bash 3.x as the default up until Catalina. As of Catalina zsh is the default for new users (and the version of zsh that ships with macOS is relatively up to date).

Alright. I never claimed it was the default shell... That was obviously csh, everyone knows that. It's a bsdism. FreeBSD's default was tcsh essentially until I stopped using it maybe 15 years ago.

Zsh was placed onto the hard drive of the computer by the operating system installation cd and was an available executable program that could be invoked from the terminal.

There, is that better?

Post reply on HN