On Fri, 21 Feb 2025 13:17:21 +0800
jeremy ardley wrote:
>
> Logging in as root on a server is highly dangerous, especially if it
> has an internet facing ssh port.
There is an approach which might be helpful here and there:
spawn a second ssh daemon with root login and bind n
On Tue, May 14, 2024 at 02:51:17PM +0200, Mario Marietto wrote:
> I've installed the Cloudflare gateway on Debian as a vm because I can't do
> it directly in FreeBSD. But I want to be covered even when I use FreeBSD.
> The script that I wrote forward the Cloudflare "VPN" from Debian to
> FreeBSD,so
I've installed the Cloudflare gateway on Debian as a vm because I can't do
it directly in FreeBSD. But I want to be covered even when I use FreeBSD.
The script that I wrote forward the Cloudflare "VPN" from Debian to
FreeBSD,so from outside my IP will be cloudFlared.
On Tue, May 14, 2024 at 1:16 P
On Tue, May 14, 2024 at 01:10:05PM +0200, Mario Marietto wrote:
> Your answer does not help me to understand how to use a "structured
> programming / if , while, for, functions" for the specific task that I want
> to achieve.
What task is that?
Your answer does not help me to understand how to use a "structured
programming / if , while, for, functions" for the specific task that I want
to achieve. I failed using "your" lovely structured programming and that's
the reason why I'm asking for some hint to understand why and how I can use
it.
On Tue, May 14, 2024 at 08:09:18AM +0200, Mario Marietto wrote:
> Nobody can show a different way,a modern way, for creating my script ? Why
> did I feel so comfortable by recreating the 1960s GOTO statement in Bash ?
I have absolutely no clue what you're trying to do or why you're trying
to do it
On Tue, May 14, 2024 at 04:54:26PM +0800, Bret Busby wrote:
>
> Wasn't sudo echo the name of a pop group?
>
> :)
If it wasn't it should've been one.
Cheers
--
t
signature.asc
Description: PGP signature
Wasn't sudo echo the name of a pop group?
:)
Bret Busby
Armadale
Western Australia
(UTC+0800)
.
On Tue, May 14, 2024 at 08:09:18AM +0200, Mario Marietto wrote:
> Nobody can show a different way,a modern way, for creating my script ? Why
> did I feel so comfortable by recreating the 1960s GOTO statement in Bash ?
I think your style is too alien to most of the people here to
make them feel the
> }
>
> Anyway, Marietto, you've got two typi:
>
> > mid :
> That should be "mid:".
>
> > jump foo
> That should be "jumpto foo".
>
> Once you've got your root-login script working, I hope you
> move on to implementing a complete open-source PL/I compiler.
>
--
Mario.
On Mon, May 13, 2024 at 08:37:16PM +0200, Erwan David wrote:
> Le 13/05/2024 à 19:45, Stefan Monnier a écrit :
[...]
> > % sudo zsh -l
> > # echo 1 > /proc/sys/net/ipv4/ip_forward
> > # ^D
> > logout
> > %
> >
> > 🙂
> >
> >
> > Stefan
> >
> >
> sudo -i will
yeah at the beginning i used xorg + xfce but then i realized that i did not
need them,so the context became the textual mode.
Il lun 13 mag 2024, 21:52 David Wright ha
scritto:
> On Mon 13 May 2024 at 21:18:30 (+0200), Mario Marietto wrote:
> > On Mon, May 13, 2024 at 9:05 PM Greg Wooledge wrot
On Mon 13 May 2024 at 21:18:30 (+0200), Mario Marietto wrote:
> On Mon, May 13, 2024 at 9:05 PM Greg Wooledge wrote:
> > On Mon, May 13, 2024 at 06:06:37PM +0200, Hans wrote:
> > > Am Montag, 13. Mai 2024, 13:24:17 CEST schrieb Greg Wooledge:
> > > > On Mon, May 13, 2024 at 07:36:07AM +0200, Richa
---> The context has been snipped out
nope. Read well what I said on my first post :
*[Forgot to say that I switched boot target to text with this command :*
*sudo systemctl set-default multi-user.target]*
What does this mean for you ? The context is that I was not using any
desktop manage
On Mon, May 13, 2024 at 06:06:37PM +0200, Hans wrote:
> Am Montag, 13. Mai 2024, 13:24:17 CEST schrieb Greg Wooledge:
> > On Mon, May 13, 2024 at 07:36:07AM +0200, Richard wrote:
> > > .profile
>
> Sorry, dumb question: Depending of the shell, the user is using (let's say,
> he
> will use bash),
Le 13/05/2024 à 19:45, Stefan Monnier a écrit :
$ su -
Password:
# echo 1 > /proc/sys/net/ipv4/ip_forward
# ^D
logout
$
I don't need no stinkin' sudo :-)
And if you only have `sudo`, but not the root password, of course:
% sudo zsh -l
# echo 1 > /proc/sys/net/ipv4/ip_forward
# ^
On Mon, May 13, 2024 at 01:45:40PM -0400, Stefan Monnier wrote:
> > $ su -
> > Password:
> > # echo 1 > /proc/sys/net/ipv4/ip_forward
> > # ^D
> > logout
> > $
> >
> > I don't need no stinkin' sudo :-)
>
> And if you only have `sudo`, but not the root password, of course:
>
> % sudo zsh -l
>
> $ su -
> Password:
> # echo 1 > /proc/sys/net/ipv4/ip_forward
> # ^D
> logout
> $
>
> I don't need no stinkin' sudo :-)
And if you only have `sudo`, but not the root password, of course:
% sudo zsh -l
# echo 1 > /proc/sys/net/ipv4/ip_forward
# ^D
logout
%
🙂
Stefan
On 5/13/24 18:52, to...@tuxteam.de wrote:
Now share your ideas :-)
$ su -
Password:
# echo 1 > /proc/sys/net/ipv4/ip_forward
# ^D
logout
$
I don't need no stinkin' sudo :-)
regards,
chris
>> If yes, second dumb question: Coiuld it be ANY script or command?
>> (also running as non-rootuser, like adding "runuser -u myuser
>> command_whatever").
>Root can do this, yes.
Or to be more precise, .bashrc (and any file that's read from it like
.bash_aliases) can run anything the bash CLI ca
I think I have found my way,adding this line to /etc/sudoers :
marietto ALL=(ALL) NOPASSWD: /usr/bin/iptables
and on the warp script :
sudo /usr/bin/iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE
On Mon, May 13, 2024 at 3:20 PM wrote:
> On Mon, May 13, 2024 at 09:17:31AM -0400, G
Since this happens so often, I'm trying to offer a recap.
As others have noted, the above
sudo echo 1 > /proc/sys/net/ipv4/ip_forward
won't work, since it runs echo under sudo, but the file opening
(that pesky ">") happens in your shell, which is probably running
unprivileged (otherwise, what
l "$cmd"
> exit
> }
Anyway, Marietto, you've got two typi:
> mid :
That should be "mid:".
> jump foo
That should be "jumpto foo".
Once you've got your root-login script working, I hope you
move on to implementing a complete open-source PL/I compiler.
Mario Marietto writes:
> There is still a problem. If I login automatically as user and inside
> the script I do this :
>
> sudo iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE
>
> it asks me for the password (don't know why it didn't before) but I
> can't issue a password,because the
etto, you've got two typi:
>
> > mid :
> That should be "mid:".
>
> > jump foo
> That should be "jumpto foo".
>
> Once you've got your root-login script working, I hope you
> move on to implementing a complete open-source PL/I compiler.
>
--
Mario.
On Mon, May 13, 2024 at 06:06:37PM +0200, Hans wrote:
> Am Montag, 13. Mai 2024, 13:24:17 CEST schrieb Greg Wooledge:
> > On Mon, May 13, 2024 at 07:36:07AM +0200, Richard wrote:
> > > .profile
>
> Sorry, dumb question: Depending of the shell, the user is using (let's say,
> he
> will use bash),
Am Montag, 13. Mai 2024, 13:24:17 CEST schrieb Greg Wooledge:
> On Mon, May 13, 2024 at 07:36:07AM +0200, Richard wrote:
> > .profile
Sorry, dumb question: Depending of the shell, the user is using (let's say, he
will use bash), can the script not be added into ~/.bashrc?
If yes, second dumb que
[image: Istantanea_2024-05-13_17-37-39.png]
Can someone explain to me why user "marietto" can't execute the command
iptables as root,without password ? thanks.
[image: Istantanea_2024-05-13_17-40-21.png]
On Mon, May 13, 2024 at 5:19 PM Mario Marietto
wrote:
> There is still a problem. If I log
There is still a problem. If I login automatically as user and inside the
script I do this :
sudo iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE
it asks me for the password (don't know why it didn't before) but I can't
issue a password,because the script inside the vm should work aut
> You don't need to, but I definitely think he does. 🙂
^^
[ Oh, bias, when will you leave me alone? ]
Stefan
I've found that solution on the Internet. It wasn't the only solution that
I found,but that form won the challenge because it has found my mind ready
to detect that it could have worked. Maybe I could have used while,but
after 1 hour of thinking I didn't understand how and I resigned. The same
for
>> > echo 1 > /proc/sys/net/ipv4/ip_forward
>> This doesn't sound right. Maybe you should investigate why you're
> No need to “investigate”, the answer is obvious: in
You don't need to, but I definitely think he does. 🙂
Stefan
Mario Marietto (12024-05-13):
> The command iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE
> doesn't work if invoked as a user,it says "you must be root". So,as
> user,the script seems to be working fine like this :
>
> function jumpto
> {
> label=$1
> cmd=$(sed -n "/$
On Mon, May 13, 2024 at 09:17:31AM -0400, Greg Wooledge wrote:
> On Mon, May 13, 2024 at 02:03:59PM +0100, Richmond wrote:
> > >> sudo xterm -e "echo 1 > hello"
>
> > Yes, but why did it allow me to delete the file? I was not root
> > then. Try it.
>
> Because you have write permission on the *di
Le 13/05/2024 à 15:03, Richmond a écrit :
Erwan David writes:
Le 13/05/2024 à 14:36, Richmond a écrit :
I was experimenting, and found this works:
sudo xterm -e "echo 1 > hello"
It created a file owned by root. But I found I was able to remove it
without being root even though group and wor
On Mon, May 13, 2024 at 02:03:59PM +0100, Richmond wrote:
> >> sudo xterm -e "echo 1 > hello"
> Yes, but why did it allow me to delete the file? I was not root
> then. Try it.
Because you have write permission on the *directory* that the file is in.
Removing (unlinking) a file is an operation th
The command iptables -A POSTROUTING -t nat -s 192.168.1.5 -j MASQUERADE
doesn't work if invoked as a user,it says "you must be root". So,as
user,the script seems to be working fine like this :
function jumpto
{
label=$1
cmd=$(sed -n "/$label:/{:a;n;p;ba};" $0 | grep -v ':$')
Richmond (12024-05-13):
> sudo bash -c "echo 1 > hello"
Use sh for that.
Regards,
--
Nicolas George
Erwan David writes:
> Le 13/05/2024 à 14:36, Richmond a écrit :
>> I was experimenting, and found this works:
>>
>> sudo xterm -e "echo 1 > hello"
>>
>> It created a file owned by root. But I found I was able to remove it
>> without being root even though group and world permissions were read
>>
writes:
> On Mon, May 13, 2024 at 01:36:23PM +0100, Richmond wrote:
>> I was experimenting, and found this works:
>>
>> sudo xterm -e "echo 1 > hello"
>
> That's like slicing your morning baguette with the chainsaw.
I do that too.
>
> But if it works for you... hey :-)
>
> Cheers
This also wo
Richmond wrote:
> I was experimenting, and found this works:
>
> sudo xterm -e "echo 1 > hello"
>
> It created a file owned by root. But I found I was able to remove it
> without being root even though group and world permissions were read
> only.
The owner of a directory can delete any file in
On Mon, May 13, 2024 at 02:53:18PM +0200, Nicolas George wrote:
> to...@tuxteam.de (12024-05-13):
> > That's like slicing your morning baguette with the chainsaw.
>
> Worse than that, it will only work from an X11 environment. Certainly
> not at boot.
The analogy to that would be that not many ki
to...@tuxteam.de (12024-05-13):
> That's like slicing your morning baguette with the chainsaw.
Worse than that, it will only work from an X11 environment. Certainly
not at boot.
Regards,
--
Nicolas George
On Mon, May 13, 2024 at 01:36:23PM +0100, Richmond wrote:
> I was experimenting, and found this works:
>
> sudo xterm -e "echo 1 > hello"
That's like slicing your morning baguette with the chainsaw.
But if it works for you... hey :-)
Cheers
--
t
signature.asc
Description: PGP signature
Le 13/05/2024 à 14:36, Richmond a écrit :
I was experimenting, and found this works:
sudo xterm -e "echo 1 > hello"
It created a file owned by root. But I found I was able to remove it
without being root even though group and world permissions were read
only.
thats because sudo exceutes a xt
I was experimenting, and found this works:
sudo xterm -e "echo 1 > hello"
It created a file owned by root. But I found I was able to remove it
without being root even though group and world permissions were read
only.
Dan Ritter (12024-05-13):
> Mario Marietto wrote:> If you run
>
> sudo echo 1 > /proc/sys/net/ipv4/ip_forward
>
> then the shell you are running it from will run "sudo echo 1"
> and then try to put the output in that file.
Other way around: the shell first tries to redirect the output to the
fi
Mario Marietto wrote:
> --> If they only want this thing to happen when root logs in directly on a
> console or ssh, then .profile may indeed be the correct answer.
>
> Yes,I don't need to run xorg and a desktop environment,since warp-cli
> disconnect and warp-cli connect do not require them.
> I
Stefan Monnier (12024-05-13):
> > echo 1 > /proc/sys/net/ipv4/ip_forward
> >
> > work only if I'm root. It does not work using sudo.
> This doesn't sound right. Maybe you should investigate why you're
> seeing this behavior, rather than work around the problem.
>
> `sudo` *is* root.
No need to “
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> work only if I'm root. It does not work using sudo.
This doesn't sound right. Maybe you should investigate why you're
seeing this behavior, rather than work around the problem.
`sudo` *is* root.
Stefan
On Mon, May 13, 2024 at 01:48:25PM +0200, Mario Marietto wrote:
> I wouldn't to login as root automatically,but I've realized that this
> command :
>
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> work only if I'm root. It does not work using sudo. So,in the end I've
> chosen to be root instead of
Le 13/05/2024 à 13:48, Mario Marietto a écrit :
--> If they only want this thing to happen when root logs in directly
on a console or ssh, then .profile may indeed be the correct answer.
Yes,I don't need to run xorg and a desktop environment,since warp-cli
disconnect and warp-cli connect do no
--> If they only want this thing to happen when root logs in directly on a
console or ssh, then .profile may indeed be the correct answer.
Yes,I don't need to run xorg and a desktop environment,since warp-cli
disconnect and warp-cli connect do not require them.
I wouldn't to login as root automati
Hello to everyone,
Richard,thanks. I've launched the script inside the .profile file that's
inside the root folder and it worked. Thank you.
Plan B : From time to time the cloudflare connection stops working,so there
is the needing to repeat these commands :
warp-cli disconnect
warp-cli connect
On Mon, May 13, 2024 at 07:36:07AM +0200, Richard wrote:
> .profile
> will always be read as soon as the user logs in, no matter how. Through a
> terminal, a GUI, doesn't matter.
That's not correct. There are many different GUI login setups where
the .profile is never read.
That said, since this
Should be as easy as executing the script from the .profile of root - that
means if "log in as root" actually means root, not just sudo'ing. .profile
will always be read as soon as the user logs in, no matter how. Through a
terminal, a GUI, doesn't matter. No idea if doing this through systemd is
e
On Sun 12/05/2024 at 22:52, Mario Marietto wrote:
> I want that the warp script is run everytime root is logged in,not more,not
> less.
The second half of this seems to do what you want
https://stackoverflow.com/a/39024841
Hello to everyone.
I'm using Debian 12. I'm configuring a little Debian 12 vm with qemu that I
will use to forward the cloudflare connection to FreeBD.
What I want to do is to run the script below as soon as root has logged in.
I've configured the automatic login of root adding to this service fi
On Fri, Sep 14, 2018 at 11:16:56AM +1000, Zenaan Harkness wrote:
> Anyone know if it's possible to get xterm (or xfce4-terminal or any
> other terminal for that matter) to be a "native/ clean login
> terminal", to increase security when running root commands?
>
ctrl-alt-F2, login will be on a con
Anyone know if it's possible to get xterm (or xfce4-terminal or any
other terminal for that matter) to be a "native/ clean login
terminal", to increase security when running root commands?
To: CypherPunks
On Thu, Sep 13, 2018 at 04:48:58PM +1000, Zenaan Harkness wrote:
> So someone cracking int
James Allsopp wrote:
> Hi,
> I need to have one computer I can ssh to other computers as root for
> Ansible. To do this I've set up a strong certificate with a password, but
> what I want is to only be able to log in as root from one IP using that
> cert. All other users should only log in via a pa
On Wed, 29 Aug 2018 13:32:56 +0100
James Allsopp wrote:
> Hi,
> I need to have one computer I can ssh to other computers as root for
> Ansible. To do this I've set up a strong certificate with a password,
> but what I want is to only be able to log in as root from one IP
> using that cert. All ot
Hi,
I need to have one computer I can ssh to other computers as root for
Ansible. To do this I've set up a strong certificate with a password, but
what I want is to only be able to log in as root from one IP using that
cert. All other users should only log in via a password and can do so from
any I
Tom Dial writes:
[...]
>From Harry's settings:
>> LoginGraceTime 120
>> PermitRootLogin without-password
Tom D wrote:
> This will prevent root login using a password. Only other methods, such
> as RSA authentication are to be permitted.
That turned out to be exact
On 06/18/17 23:08, David Christensen wrote:
...
You should see host2's ECDSA key fingerprint the first time you log in.
Verify it against the note card.
Correction: You should see host1's ECDSA key fingerprint ...
David
On 06/18/17 08:57, Harry Putnam wrote:
...
root # cat /etc/debian_version
8.8
root # uname -a
Linux d2 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2 (2017-04-30) x86_64 GNU/Linux
root # dpkg-query --show openssh-server
openssh-server 1:6.7p1-5+deb8u3
root # dpkg-query --show openssh-client
openssh-c
On 06/18/2017 09:57 AM, Harry Putnam wrote:
> David Christensen writes:
>
>> On 06/12/2017 06:39 AM, Harry Putnam wrote:
>>> Running debian jesse in a vbox vm on a Solaris host
>>>
>>> I have what seems like an unusual problem with root login on this
&g
Harry Putnam writes:
>>
>> # ls -1 /root/.ssh
>>
Sorry ... I managed to overlook this one:
root # ls -la .ssh
total 12
drwx-- 2 root root 4096 May 30 21:44 .
drwx-- 6 root root 4096 Jun 18 11:35 ..
-rw-r--r-- 1 root root 666 May 30 22:17 known_hosts
Harry Putnam writes:
>>
>> # ls -1 /root/.ssh
>>
Sorry ... I managed to overlook this one:
root # ls -la .ssh
total 12
drwx-- 2 root root 4096 May 30 21:44 .
drwx-- 6 root root 4096 Jun 18 11:35 ..
-rw-r--r-- 1 root root 666 May 30 22:17 known_hosts
David Christensen writes:
> On 06/12/2017 06:39 AM, Harry Putnam wrote:
>> Running debian jesse in a vbox vm on a Solaris host
>>
>> I have what seems like an unusual problem with root login on this
>> host.
[...]
>> I'm fresh out of ideas as to what els
On 12-06-17, Erik Karlin wrote:
> On Mon, Jun 12, 2017 at 08:06:21PM +0200, Dejan Jocic wrote:
> > On 12-06-17, Felix Miata wrote:
> > > Jan-Peter Rühmann composed on 2017-06-12 17:15 (UTC+0200):
> > > .
> > > > Normally you can´t login via Root, because there is no entry in the
> > > > passwd fil
On 06/12/2017 06:39 AM, Harry Putnam wrote:
Running debian jesse in a vbox vm on a Solaris host
I have what seems like an unusual problem with root login on this
host.
I've done the normal things one does to allow root login; that is, add
PermitRootLogin yes
to /etc/ssh/sshd_c
On 12-06-17, Felix Miata wrote:
> Jan-Peter Rühmann composed on 2017-06-12 17:15 (UTC+0200):
> .
> > Normally you can´t login via Root, because there is no entry in the passwd
> > file.
> .
> That is false for every Debian installation (Squeeze, Wheezy, Jessie, Stretch
> at
> least) I have ever d
Jan-Peter Rühmann composed on 2017-06-12 17:15 (UTC+0200):
.
> Normally you can´t login via Root, because there is no entry in the passwd
> file.
.
That is false for every Debian installation (Squeeze, Wheezy, Jessie, Stretch at
least) I have ever done (unless maybe I'm misremembering all the way
schrieb Harry Putnam:
> Running debian jesse in a vbox vm on a Solaris host
>
> I have what seems like an unusual problem with root login on this
> host.
>
> I've done the normal things one does to allow root login; that is, add
>
>PermitRootLogin yes
>
> to /etc/s
Running debian jesse in a vbox vm on a Solaris host
I have what seems like an unusual problem with root login on this
host.
I've done the normal things one does to allow root login; that is, add
PermitRootLogin yes
to /etc/ssh/sshd_config
Restart ssh, and in fact this host has
Dear All,
I have two machines for testing some services on jessie. however i can not
allow access to root remote ssh.
i have read this on saveral places that
/etc/ssh/ssh_config has a line PermitRootLogin without-password which has
to be change to yes
first of all i can not find this line in who
e without-password directive, esp. if ssh port is
> accessiable in public networks.
>
> Best,
>
> Tobias
>
>
>
>
>
> ------
> Date: Wed, 3 Feb 2016 12:11:45 +0500
> Subject: Re: root login in Jessie
> From: sir...@gmail.com
> To: t
You probaly forgot to restart ssh after changing the config?
Best,
Date: Wed, 3 Feb 2016 11:43:40 +0500
Subject: root login in Jessie
From: sir...@gmail.com
To: debian-user@lists.debian.org
Dear All,
I have two machines for testing some services on jessie. however i can not
allow access to
On Lu, 17 mar 14, 08:43:24, Scott Ferguson wrote:
> On 17/03/14 04:44, Andrei POPESCU wrote:
> > On Du, 16 mar 14, 01:24:03, Scott Ferguson wrote:
> >>
> >> In the spirit of investigation I tried testing a few methods of
> >> disabling root login (there are
On 17/03/14 04:44, Andrei POPESCU wrote:
> On Du, 16 mar 14, 01:24:03, Scott Ferguson wrote:
>>
>> In the spirit of investigation I tried testing a few methods of
>> disabling root login (there are likely other methods)
>
> AFAIK the installer uses 'passsw
On Du, 16 mar 14, 01:24:03, Scott Ferguson wrote:
>
> In the spirit of investigation I tried testing a few methods of
> disabling root login (there are likely other methods)
AFAIK the installer uses 'passswd -l'.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFrom
til then we're just speculating.
>
> Cheers, Tom
>
In the spirit of investigation I tried testing a few methods of
disabling root login (there are likely other methods)
Expiring the root password:-
# chage -E 0 root
This prohibits login to a console as root, but...
Booting into
On Tue, 9 Dec 2008 10:09:09 +0700
"Zaki Akhmad" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> How do I implement more restrict access control? I want to disable
> root login directly from Internet. So someone must login first as a
> user then after successfully login as u
Hi,
How do I implement more restrict access control? I want to disable
root login directly from Internet. So someone must login first as a
user then after successfully login as user he/she login as a root.
--
Zaki Akhmad
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On Wed, Aug 15, 2007 at 12:32:13PM +0800, Huang, Kuan-Chung wrote:
> PROBLEM 2:
> I press the "software update" button at the right-up coner on the screen, the
> system prompts to enter administrative password.
> BUT, during installating the system, it never prompts any messages for
> setting u
1. I use netinst CD to Install "etch" on my PC (Intelx86 - CPU is AMD duron
800MHz) with the following boot parameters:
expert modules=ppp-udeb
2. The language for installation is zh_TW (Chinese traditional) and the
keyboard mapping is US.
3. During installation I choose to NOT
please help if you have
solution.
Regards,
Ashvin barevadia
-Original Message-
From: Mark [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 23, 2006 3:16 PM
To: debian-user@lists.debian.org
Subject: Re: Root Login invalid
On Tue, May 23, 2006 at 12:58:56PM +0530, Ashvin Barevadia wr
root is not permited to login in X by default
if you use gdm, then on the login screen
go to 'configure' it will ask the root password
the search there where you check 'permit root login'
--
Henrique G. Abreu
[EMAIL PROTECTED]
On Tue, May 23, 2006 at 12:58:56PM +0530, Ashvin Barevadia wrote:
>Dear All,
>
>I am not able to login as root it's giving error "invalid login" even
>it's not asking password, so I have tried to login as su but it gives
>error "su authentication failure", please help me.
Found using a very popula
On Tue, May 23, 2006 at 12:58:56PM +0530, Ashvin Barevadia wrote:
> Dear All,
>
>
>
> I am not able to login as root it's giving error "invalid login" even it's
> not asking password, so I have tried to login as su but it gives error "su
> authentication failure", please help me.
>
>
Whose
Dear All,
I am not able to login as root it’s
giving error “invalid login” even it’s not asking password,
so I have tried to login as su but it gives error “su authentication
failure”, please help me.
Regards,
Ashvin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Lamb wrote:
> Andreas Ntaflos wrote:
>
>>however, fails. No matter what password is entered, the system refuses to
>>let us in as root. The root-password can be changed without problem
>>when `su'-ed to root so the problem is not that it's misty
Andreas Ntaflos wrote:
> however, fails. No matter what password is entered, the system refuses to
> let us in as root. The root-password can be changed without problem
> when `su'-ed to root so the problem is not that it's mistyped at the
> prompt or anything.
What does /etc/securetty say?
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Ntaflos wrote:
> Thanks for the replies! I am certain that the machine is not compromised
> since the only time it's used only on the company's internal network
> (and there's nobody there who could or would compromise a Unix machine).
>
> My
On Mon, Jul 25, 2005 at 08:12:53 -0500, Kent West wrote:
> Andreas Ntaflos wrote:
>
> >A colleague of mine set up a Debian 3.1 (or was ist 3.0?) box a couple
> >of months ago and has had the following problem since then:
> >
> >When booting the machine everything seems fine and it gets to the logi
On Mon, 2005-07-25 at 08:12 -0500, Kent West wrote:
> Andreas Ntaflos wrote:
>
> >A colleague of mine set up a Debian 3.1 (or was ist 3.0?) box a couple
> >of months ago and has had the following problem since then:
> >
> >When booting the machine everything seems fine and it gets to the login
> >
Andreas Ntaflos wrote:
>A colleague of mine set up a Debian 3.1 (or was ist 3.0?) box a couple
>of months ago and has had the following problem since then:
>
>When booting the machine everything seems fine and it gets to the login
>prompt eventually. There every non-system, non-root user can login
essary or anything, but I'd like to know anyway
what (if anything) went wrong during the installation. Can't be normal
behaviour to have no consoles and no root login available, can it?
Thanks in advance for any pointers!
Andreas
--
Andreas "daff" Ntaflos
daff AT dword DOT org
Felixk Karpfen wrote:
On 2004-11-21, Jules Dubois <[EMAIL PROTECTED]> wrote:
On Fri, 19 Nov 2004 13:50:38 -0500, Williams, Allen wrote:
4. I can't log in to the X desktop as root. Where do I fix that?
It's a security feature. If you're using GDM, there's a configuration
option at the login scre
1 - 100 of 204 matches
Mail list logo
