Hi List,
i am using dropbear is a script and was testing error codes.
I noticed that DB returns 0 (success) even when authentication does not work.
(OpenSSH returns here 255).
Is there somewhere a list of error codes to find ?
General i noticed that the errorcodes are not divers enough so i had
Am 19.05.2017 16:34, schrieb Henrik Uggla:
> Permission to run one command, everything else should be denied.
why not modify .profile (or /bin/sh in /etc/profile) ?
anything else feels complicated.
re,
wh
>
> /HU
>
> Från: Matt Johnston
Am 19.05.2017 09:42, schrieb Henrik Uggla:
> Hi!
>
>
> How can I set restrictions, like those given in authorized_keys, to all
> password logins?
>
>
did you try the generalsetup at /etc/ssh/ssh_config ?
re,
wh
> regards
>
> HU
>
Hello Hari,
nothing special just a hint
when sending logs just replace real IPs with something like 192.168.1.*
otherwise you may reveal information you do not want to reveal.
Just remember that searchengines will find you post now and in 10 years.
re,
wh
Am 23.10.2017 13:12, schrieb
> Hans Harder hat am 4. August 2018 um 12:58 geschrieben:
>
>
> Underneath the patch against the current git version
> Hans
>
> diff -w dropbear-git/cli-runopts.c dropbear-patch/cli-runopts.c
> --- dropbear-git/cli-runopts.c
> +++ dropbear-patch/cli-runopts.c
> @@ -629,9 +629,7 @@
>
> Matt Johnston hat am 1. März 2019 um 15:24 geschrieben:
>
>
> Hi Mike,
>
> The limit's arbitrary so 32 would be fine. Maybe even something like 100.
> I'll increase it for the next release.
>
> Cheers,
> Matt
>
> > On Fri 1/3/2019, at 8:28 am, W. Michael Petullo wrote:
> >
> >
Am 12.12.2019 13:01, schrieb Joakim Tjernlund:
> On Wed, 2019-12-11 at 18:00 +0100, Joakim Tjernlund wrote:
>> On Wed, 2019-12-11 at 23:53 +0800, Matt Johnston wrote:
>>> Hi Joakim,
>>>
>>> The server needs to be stopped and restarted. If this is for new keys at
>>> first-boot you could look at
This is caused by changes in ssh_config. You can try:
ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 USER@TARGET
or persistent in ssh_config
KexAlgorithms=+diffie-hellman-group1-sha1
your mileage may vary etc.
re,
wh
Von: Dropbear
Hello List,
actually i expected this would be a FAQ but i can not find an answer:
How can i restrict the hosts that are allowed to access the
dropbear server ?
re,
wh
that be acceptable ?
re,
wh
Von: Dropbear im Auftrag von Sebastian Gottschall
Gesendet: Donnerstag, 20. Mai 2021 15:53
An: dropbear@ucc.asn.au
Betreff: Re: restrict access
isnt that a job for netfilter?
Am 20.05.2021 um 15:23 schrieb Walter Harms
u, May 20, 2021 at 5:05 PM Sebastian Gottschall
> wrote:
>> what about a feature like blocking a client for N minutes if more than N
>> times of failed logins. its relativily easy to implement and lows down
>> brute force attacks
>>
>> Am 20.05.2021 um 16:44 schrieb
: Steffen Nurpmeso
Gesendet: Dienstag, 25. Mai 2021 02:40:50
An: Walter Harms
Cc: dropbear@ucc.asn.au
Betreff: Re: restrict access
WARNUNG: Diese E-Mail kam von außerhalb der Organisation. Klicken Sie nicht auf
Links oder öffnen Sie keine Anhänge, es sei denn, Sie kennen den/die
Absender*in und wissen
lately there was a discussion who to restrict access to a dropbear server. The
result were some solutions outside dropbear. I have attached a patch to show
how this could be done. It uses fnmatch() what means the patch is small and the
pattern is simple. (Try -D 192.168.1.*)
re,
wh
---
would it be possible to add an option to add an non-interactive mode ?
Getting yes/no questions (or else) in a script is clearly not helpful.
re,
wh
Von: Dropbear im Auftrag von Matt Johnston
Gesendet: Montag, 21. November 2022 16:20:25
An: M Rubon
14 matches
Mail list logo
