(Kali Linux User Only) .bashrc File Is Messed Up.

Changing umask value for files and directories take effect after reload:
/etc/profile
/etc/bashrc
default permission for all users:
-rw-r--r--
above permission is edited to:
-rw-rw-r--
If a specific user in group having only read permission to a file/directory is created before reload,and Linux server reloads, that user gets rw permission to that file/directory. what is the alternative of securing:
/etc/profile
/etc/bashrc
apart from giving the two files access to root user only, and locking out all other users?

Good day everyone,

I'm currently a student and as far as I'm aware I still need windows for some program I need, but I am going over to Linux.
(Thus I'm running Windows 8 at this moment)

Today I was going to install Ubuntu 14.04.01 alongside Windows 8, everything went well till I hit the 4th step (Installation type page) of the installation:

A message like follows showed:
"This computer currently has Debian GNU/Linux (Kali Linux 1.0.7) on it. What would you like to do?"

There are then 3 options available:
1) Install Ubuntu alongside Debian GNU/Linux (Kali Linux 1.0.7)
2) Replace Debian GNU/Linux (Kali Linux 1.0.7) with Ubuntu
3 and 4 is greyed out.
5) Something else (You can create resize partitions yourself, or choose multiple partitions for Ubuntu.

I just want to make sure what option to choose, I cant afford to lose all my data and windows.

Problem: Showing Kali Linux as current OS and not Windows 8.

Possible reason for showing Kali Linux as current OS:
I have a live CD of Kali Linux and ran it a few times in the past, but according to my knowledge it shouldn't have changed anything.

Maybe the 1st option is still the right one even though the current OS isn't listed right? Or the 3rd option is like a manual setting I guess.

Thanks for the time reading and helping!

On kali, how do i split a 15.7gb text file into 3 parts ? Also when i split the text file i don't want words to be incomplete from the split. Please help on how to exactly do it. Writing the exact commands to my specific situation would help me out a lot. Thanks in advance.

I am trying to install Kali-Linux. and I get a message that I have the wrong installer kernal that doesn't match. what do I do??? the attachment is a pic of the warning.

Hi everyone, I am a new member and also new to linux, I encountered a problem, but last week I tried but did not solve
I downloaded iso file linux 1.1.0 on page potassium https://www.kali.org, I installed on my Dell inspiron n4010, it works very well and does not have any errors, but after I update and upgrade all packages, I rebooted the system switches to the command line, I lost a lot of time to return to the graphics, but when booting up the network manager icon not seen, I have set the package network-manager-gnome_0.9.4.1-0ubuntu2_i386.deb network manager icon show but when click on the network manager icon only contained text "network manager is not running."
I also installed Wicd but could not run "could not connect to wicd's D-Bus interface. Check the wicd log for error messages."
wireless driver apparently was set before
root@kali:~# airmon-ng
PHY Interface Driver Chipset

phy0 wlan0 wl Broadcom Corporation BCM4313 802.11b/g/n (rev 01)

please help me!
please guide installed offline, my kali linux no internet connection. can download package from another machine to install.

Centos 6.5

I ran into an interesting problem (on reddit) that I figured I could solve, but I have not been able to. Its simple,.. I added 'exit 0' to /root/.bashrc, and now I am trying to log in via ssh.

Everytime I do, it immediately exits when it runs the .bash_profile, which sources .bashrc, (which is immediate upon 'logging in')

I've tried:

Code:

ssh root@192.168.1.50 -t vim
vim scp://192.168.1.50/.bashrc
vim scp://192.168.1.50/root/.bashrc
ssh root@192.168.1.50 bash --norc
ssh root@192.168.1.50 /bin/bash --norc --noprofile
ssh -T root@192.168.1.50 "mv /root/.bashrc /root/.bashRC"
scp .bashrc root@192.168.1.50:/root/
ssh root@192.168.1.50 /bin/bash --norc --noprofile -vvvvvvvvvv
ssh -vvvvvv root@192.168.1.50 /bin/bash --norc --noprofile
ssh -vvvvvv root@192.168.1.50 /bin/mv /root/.bashrc /root/.bashRC
ssh -t -t root@192.168.1.50 << EOF
mv /root/.bashrc /root/.bashRC
EOF
ssh -t -t root@192.168.1.50 --norc << EOF
echo HELLO > /root/.bashrc
EOF
ssh -tv root@192.168.1.50 rm .bashrc

So,.. I am unable to get back into the system (as root, no other users exist) after adding 'exit 0' to .bashrc

Anyone feel like explaining why all of these failed (aside from saying SSH interactive logins run the .bash_profile/.bashrc files) or, offering a suggestion that works? Seems like if you have the root password, you should be allowed to modify the login process... since... you know... you are root.

I had Kali and Linux Mint installed and erased Mint to install Centos7. Grub was totally deleted and I could only boot into grub recovery. Many hours of cussing later I got Kali back, I can see Centos filesystem mounted on my desktop and in disk utility. I never finished setting Centos up as I was rushed out the door which probably caused the problem in the first place, for some reason it's raid and although it's 2 harddrives they are not set up for raid and 1 is Kali and 1 is Centos. The Centos boot folder is still empty after running grub-install on it twice and it does not show in grub. How do I get Centos as an option?

how do i input this into the CLI?

Create two new files a.txt and b.txt, create a tarball of the two files

using kali linux on windows 7

hi there once again
Now I am getting this problem which running the cmd "honeyd -d -f honeyd.conf"
root@kali:/etc/honeypot# honeyd -d -f honeyd.conf
Honeyd V1.5c Copyright (c) 2002-2007 Niels Provos
honeyd[4726]: started with -d -f honeyd.conf
honeyd[4726]: listening promiscuously on eth0: (arp or ip proto 47 or (udp and src port 67 and dst port 68) or (ip )) and not ether src 98:4b:e1:94:62:46
honeyd[4726]: [eth0] trying DHCP
honeyd[4726]: Demoting process privileges to uid 65534, gid 65534
honeyd[4726]: [eth0] got DHCP offer: 192.168.23.2
honeyd[4726]: Updating ARP binding: 00:00:24:26:26:1d -> 192.168.23.2
honeyd[4726]: arp reply 192.168.23.2 is-at 00:00:24:26:26:1d
honeyd[4726]: TTL exceeded for dst 224.0.0.22 at gw 10.0.0.1
honeyd[4726]: No reverse routing map for 10.0.0.1
honeyd[4726]: TTL exceeded for dst 224.0.0.22 at gw 10.0.0.1
honeyd[4726]: No reverse routing map for 10.0.0.1
honeyd[4726]: TTL exceeded for dst 224.0.0.22 at gw 10.0.0.1
honeyd[4726]: No reverse routing map for 10.0.0.1
honeyd[4726]: TTL exceeded for dst 224.0.0.22 at gw 10.0.0.1
honeyd[4726]: No reverse routing map for 10.0.0.1

what does it mean? because it starts to spam the terminal with such errors. or it is not??

I think, I have to edit the "honeyd.conf" file, but no clue.
the following is my honeyd configuration.

route entry 10.0.0.1
route 10.0.0.1 link 10.2.0.0/24
route 10.0.0.1 add net 10.3.0.0/16 10.3.0.1 latency 8ms bandwidth 10Mbps
route 10.3.0.1 link 10.3.0.0/24
route 10.3.0.1 add net 10.3.1.0/24 10.3.1.1 latency 7ms loss 0.5
route 10.3.1.1 link 10.3.1.0/24

# Example of a simple host template and its binding
create template
set template personality "Microsoft Windows XP Professional SP1"
set template uptime 1728650
set template maxfds 35
# For a complex IIS server
add template tcp port 80 "sh /usr/share/honeyd/scripts/win32/web.sh"
add template tcp port 22 "/usr/share/honeyd/scripts/test.sh $ipsrc $dport"
add template tcp port 23 proxy $ipsrc:23
add template udp port 53 proxy 141.211.92.141:53
set template default tcp action reset
# Use this if you are not running honeyd as 'honeyd' user:
# Debian-specific (use nobody = 65534 instead of 32767)
# set template uid 65534 gid 65534

create default
set default default tcp action block
set default default udp action block
set default default icmp action block

create windows
set windows personality "Microsoft Windows XP Professional SP1"
set windows default tcp action reset
add windows tcp port 135 open
add windows tcp port 139 open
add windows tcp port 445 open

set windows ethernet "00:00:24:ab:8c:12"
dhcp windows on eth0


urgent help needed please. thanks in advance

I made the mistake of adding an xterm invocation to my ".bashrc" file. My intent was to simply execute an xterm upon initial login to the KDE environment on Debian Wheezy (though the distro probably would have made no difference). What happened is that with each invocation of "xterm", the new xterm would again invoke an "xterm" via the ".bashrc" file. Duh, infinite recursion of xterms upon login. Is there a simple way to invoke an xterm at login that doesn't itself lookup the ".bashrc" file? By the time someone answers this, I will probably find and answer somewhere in the bash/xterm man pages, but thought I'd throw it out there. Really felt stupid after having realized my mistake. Had to login to recovery command line mode and replace the ".bashrc" file with "/etc/skel/.bashrc". Cheerio