9da8a63dd4
We're starting to see developers use subkeys of their primary key to sign packages, which we aren't handling well in the web interface. These subkeys show up as unknown, which isn't strictly true. Start the process of being able to handle these keys by adding a model that will store all known keys and subkeys and the relationships among them, as well as which developer owns each. Signed-off-by: Dan McGee <dan@archlinux.org>
46 lines
1.4 KiB
Python
46 lines
1.4 KiB
Python
from django.contrib import admin
|
|
from django.contrib.auth.admin import UserAdmin
|
|
from django.contrib.auth.models import User
|
|
|
|
from .models import UserProfile, MasterKey, DeveloperKey, PGPSignature
|
|
|
|
|
|
class UserProfileInline(admin.StackedInline):
|
|
model = UserProfile
|
|
|
|
|
|
class UserProfileAdmin(UserAdmin):
|
|
inlines = [UserProfileInline]
|
|
list_display = ('username', 'email', 'first_name', 'last_name', 'is_staff', 'is_active')
|
|
list_filter = ('is_staff', 'is_superuser', 'is_active')
|
|
|
|
|
|
class MasterKeyAdmin(admin.ModelAdmin):
|
|
list_display = ('pgp_key', 'owner', 'created', 'revoker', 'revoked')
|
|
search_fields = ('pgp_key', 'owner__username', 'revoker__username')
|
|
date_hierarchy = 'created'
|
|
|
|
|
|
class DeveloperKeyAdmin(admin.ModelAdmin):
|
|
list_display = ('key', 'parent', 'owner', 'created', 'expires', 'revoked')
|
|
search_fields = ('key', 'owner__username')
|
|
list_filter = ('owner',)
|
|
date_hierarchy = 'created'
|
|
|
|
|
|
class PGPSignatureAdmin(admin.ModelAdmin):
|
|
list_display = ('signer', 'signee', 'created', 'expires', 'valid')
|
|
list_filter = ('valid',)
|
|
search_fields = ('signer', 'signee')
|
|
date_hierarchy = 'created'
|
|
|
|
|
|
admin.site.unregister(User)
|
|
admin.site.register(User, UserProfileAdmin)
|
|
|
|
admin.site.register(MasterKey, MasterKeyAdmin)
|
|
admin.site.register(DeveloperKey, DeveloperKeyAdmin)
|
|
admin.site.register(PGPSignature, PGPSignatureAdmin)
|
|
|
|
# vim: set ts=4 sw=4 et:
|