Hi,

I wasn't convinced about changing the 'admin' path until recently. My reasons 
to change the path of 'admin' are:

-A bit less likely to be affected by bugs like
https://docs.djangoproject.com/en/3.1/releases/3.0.1/#cve-2019-19844-potential-account-hijack-via-password-reset-form
: at least the site wouldn't appear in automatic scans for
vulnerabilities (if checking Django versions based on the admin
template, etc.) . The bug/exploit might have been known before the fix
was implemented (and everyone updated) so I prefer to not be exposed (or
less exposed)

-At the moment in Django there is no rate-limiting login attempts "out
of the box" so I prefer to avoid the opportunity if possible

-Partially out of my control: an 'admin' user might have used the same
password in another place and the password got leaked

Other people might have other reasons.

Cheers,

On Nov/18/2020, Tim Graham wrote:
> I'm not convinced that a system check promoting security by obscurity adds 
> much value. The original poster wrote "sometimes it can be a security 
> concern." Maybe that's the case (how so?) but for most sites I would say 
> it's not.
> On Wednesday, November 18, 2020 at 7:33:47 AM UTC-5 Carles Pina Estany 
> wrote:
> 
> >
> > Hi,
> >
> > On Nov/16/2020, Carles Pina i Estany wrote:
> >
> > > Either way: I'd be happy to write a django check to make sure that
> > > 'admin/' is not routed to admin.
> >
> > Regarding this check: this morning I've done a very preliminary/for fun
> > draft to play with.
> >
> >
> > https://github.com/cpina/django/commit/199c2fb26dc6b323195b8136bda596d1cc9857f1
> >
> > I'm not sure what is the best way to check if /admin is routed to
> > django.contrib.admin. At the moment it's doing:
> >
> > resolve(admin_url)._func_path == 'django.contrib.admin.sites.index'
> >
> > Yes, I know! :-)
> >
> > I could also do something along the lines of:
> > resolve(admin_url).func.admin_site == admin.site
> >
> > This causes problems on the unit test side (need to import admin.site).
> > Still I don't really like it.
> >
> > Does anyone have any better suggestions or comments? (or code pointer).
> > Otherwise later on I'll have another look.
> >
> > Thank you very much,
> >
> > -- 
> > Carles Pina i Estany
> > https://carles.pina.cat
> >
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers  (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/df485a53-2ad2-461f-95c8-f8f3857d67dbn%40googlegroups.com.

-- 
Carles Pina i Estany
https://carles.pina.cat

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/20201118211506.GA4744%40pina.cat.
  • ... Shoury Sharma
    • ... Arvind Nedumaran
      • ... Adam Johnson
        • ... Carles Pina i Estany
          • ... Carles Pina i Estany
            • ... Tim Graham
              • ... Carles Pina i Estany
                • ... Carlton Gibson
                • ... Shoury Sharma
                • ... Carlton Gibson
                • ... r...@whidbey.com
                • ... Arvind Nedumaran
                • ... Collin Anderson
                • ... 'Aaron C. de Bruyn' via Django developers (Contributions to Django itself)
                • ... Collin Anderson
                • ... 'Aaron C. de Bruyn' via Django developers (Contributions to Django itself)
                • ... Daryl

Reply via email to