Result for 8CFE5119A5EE7BF4D77A345E9C497ACE653450D5

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/repoze/what/authorize.pyo
FileSize1437
MD55678455D142AF5EAE6A6CBA355A74BB0
SHA-18CFE5119A5EE7BF4D77A345E9C497ACE653450D5
SHA-25641030352811142B9D0A2D4C86FEB4A0352A1AFA24F5DDD54F5CF422A073584D9
SSDEEP24:8SxPkHAc9/1Uv+sAL/Xl/ylsOguBtDFz41UvDdUsscQWDE0P6QLNwtt1aBLWug8M:84AAk/uhKl/y2otDFz4ubWQHDECNU1YO
TLSHT14F21C0BEE5920833F4222076E96025E35AE9C06B83D02E90715C886D3F9E7D5C57FB91
hashlookup:parent-total28
hashlookup:trust100

Network graph view

Parents (Total: 28)

The searched file hash is included in 28 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD59D410EA11E03B322925DE9DF4703B200
PackageArchnoarch
PackageDescription`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainerFedora Project
PackageNamepython-repoze-what
PackageRelease5.fc19
PackageVersion1.0.9
SHA-1070F45F06BE797853C004A86D3C07B6F8E8BA715
SHA-25600BB5CBFBCC601305150347D00BCB975D354B4FF787BCA16AACFF9F0831F7A29
Key Value
MD5C6920F53DCCB6DD5C13794F50D9CC740
PackageArchnoarch
PackageDescription`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainerFedora Project
PackageNamepython-repoze-what
PackageRelease4.fc18
PackageVersion1.0.9
SHA-10EF917C066280FDA47C9DC0E89B67CD9D2BDC940
SHA-25613F848152EE0857EED959755F25160D15931DD8066E358E439DB726A5A68FBB0
Key Value
MD57E456AA6C6021D28F304F0092ABD8BAC
PackageArchnoarch
PackageDescription`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainerFedora Project
PackageNamepython-repoze-what
PackageRelease5.fc19
PackageVersion1.0.9
SHA-114CF0FA408D86AA7FEDAD6175DBCD509062B574A
SHA-2562995AA27805467DFF8E7540247F7C052B10EFE1D47BE8BCEE53B1000F85CC7B9
Key Value
MD5744B0C9A6647C41BC15A3DFFCEE222C0
PackageArchnoarch
PackageDescription`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainerFedora Project
PackageNamepython-repoze-what
PackageRelease5.fc19
PackageVersion1.0.9
SHA-11EC710E091A5752E9A6B64BA07B017260CC9B0EE
SHA-256FE3402DC9B376F8B7F54598FC253ABC7D9474F08B772DA1BF7FFA31732E4F530
Key Value
MD5935C54BEA287CF6C48005D6C8BAE130C
PackageArchnoarch
PackageDescription`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainerFedora Project
PackageNamepython-repoze-what
PackageRelease5.fc19
PackageVersion1.0.9
SHA-1212824B5D39AA6A16ADFDE012FAAFDF4D5D4D89B
SHA-256CE18ABC5CA7692A47B807E3AF7F320438865757277EF2E5F27B3377865E8F666
Key Value
MD5DB611815487F10C16A88989C66B4D9FB
PackageArchnoarch
PackageDescription`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainerFedora Project
PackageNamepython-repoze-what
PackageRelease12.fc24
PackageVersion1.0.9
SHA-128B53971423276752B22C27EF7C6D3DE10F2CCFB
SHA-25616D9632A505ED30CE97838E2F67F086F706A8D03F40CEF507F3B42891903DBCA
Key Value
MD52811AFEB9E512434B0520C34F605377E
PackageArchnoarch
PackageDescription`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainerFedora Project
PackageNamepython-repoze-what
PackageRelease11.fc23
PackageVersion1.0.9
SHA-12B4CCCC4B1F7497F1C16334BBAA67F550557DDB7
SHA-256C6AEF059C529B05E0D93962DD6BDA1976DC059CDFA524F8DE5189F0D9884CC4D
Key Value
MD5DCB83949C6E38CB9292B62333F4C52AA
PackageArchnoarch
PackageDescription`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainerFedora Project
PackageNamepython-repoze-what
PackageRelease2.fc15
PackageVersion1.0.9
SHA-135971854869BE06B87067FF06EB66172DFECB3B7
SHA-256B257C52610C914BA31261626910F930486FA18CE45B20441B1759B19842DA3D0
Key Value
MD5662A0BA156D9548C2F1D52C9C402CA52
PackageArchnoarch
PackageDescription`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainerFedora Project
PackageNamepython-repoze-what
PackageRelease3.fc17
PackageVersion1.0.9
SHA-137D43BCD08B5A8B537B311397585E962B6D0A93D
SHA-25668055A964346418AB40D99E3A99DC42207257ECAEF906DDAE8E48FAD1DC6EEFC
Key Value
MD5A95924ABDA6DF7FF70E3740C5B9CAB40
PackageArchnoarch
PackageDescription`repoze.what` is an `authorization framework` for WSGI applications, based on `repoze.who` (which deals with `authentication`). On the one hand, it enables an authorization system based on the groups to which the `authenticated or anonymous` user belongs and the permissions granted to such groups by loading these groups and permissions into the request on the way in to the downstream WSGI application. And on the other hand, it enables you to manage your groups and permissions from the application itself or another program, under a backend-independent API. For example, it would be easy for you to switch from one back-end to another, and even use this framework to migrate the data. It's highly extensible, so it's very unlikely that it will get in your way. Among other things, you can extend it to check for many other conditions (such as checking that the user comes from a given country, based on her IP address, for example).
PackageMaintainerFedora Project
PackageNamepython-repoze-what
PackageRelease4.fc18
PackageVersion1.0.9
SHA-13A5988133030C9BDD314224DB64358477B3AAC87
SHA-256568D471660821BC1F17F626F5A5B4DAD3481E6EE8D105580D532EEBC7491D4CB