1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
|
%global _empty_manifest_terminate_build 0
Name: python-django-dreiattest
Version: 0.0.31
Release: 1
Summary: please add a summary manually as the author left a blank one
License: MIT
URL: https://github.com/dreipol/django-dreiattest
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/a9/f1/0d10d54e02f94eb39d80ac59e466d33982ea9834ca66ae662ef21a2e6cae/django-dreiattest-0.0.31.tar.gz
BuildArch: noarch
Requires: python3-pyattest
%description
# django-dreiattest
dreiattest leverages [pyttest](https://github.com/dreipol/pyattest) and integrates it into django. It handles routing, different config options and persistence of tokens and public keys. To use dreiAttest you need to use the corresponing libraries for [iOS](https://github.com/dreipol/dreiAttest-ios) and [Android / Kotlin Multiplatform](https://github.com/dreipol/dreiAttest-android).
## Installation
dreiAttest is available on PyPI and can be installed via `$ python -m pip install dreiattest-django`.
After the installation make sure to add `dreiattest` to your `INSTALLED_APPS` and trigger all migrations
with `python manage.py migrate dreiattest`. Also, you need to register the default endpoints in your urls.py
```
urlpatterns = [
path('admin/', admin.site.urls),
path('', include('dreiattest.urls')),
...
]
```
## Config
There are multiple settings you can and or have to set in your settings.py. The following are mandatory:
- **Apple**: `DREIATTEST_APPLE_APPID`
- **Google (Legacy: Safety Net)**: `DREIATTEST_GOOGLE_APK_NAME`, `DREIATTEST_GOOGLE_APK_CERTIFICATE_DIGEST`
- **Google Play Integrity API**: `DREIATTEST_GOOGLE_APK_NAME`, `DREIATTEST_GOOGLE_DECRYPTION_KEY`, `DREIATTEST_GOOGLE_VERIFICATION_KEY`
These are all the possible config values and what they do.
- DREIATTEST_BASE_URL: Our different endpoints like /key and /nonce will be bellow this slug
- DREIATTEST_UID_HEADER: Header containing the DeviceSession uid
- DREIATTEST_ASSERTION_HEADER: Header containing the assertion
- DREIATTEST_USER_HEADERS_HEADER: Header containing the list of comma separated headers that are included in the assertion
- DREIATTEST_NONCE_HEADER: Header containing the server nonce that was used inside the attestation
- DREIATTEST_BYPASS_HEADER: Header containing the shared secret to bypass the verification process. Helpfull for debugging
- DREIATTEST_APPLE_APPID: Header containing the apple app id
- DREIATTEST_GOOGLE_APK_NAME: Header containing the google apk name
- DREIATTEST_GOOGLE_DECRYPTION_KEY: A Base64 encoded AES key secret as described [here](https://developer.android.com/google/play/integrity/verdict#decrypt-verify)
- DREIATTEST_GOOGLE_VERIFICATION_KEY: A Base64 encoded public key as described [here](https://developer.android.com/google/play/integrity/verdict#decrypt-verify)
- DREIATTEST_PRODUCTION: Indicating if we're in a production environment or not. Some extra verifications are made if this is true. Those are described in the [pyttest](https://github.com/dreipol/pyattest) readme.
- DREIATTEST_GOOGLE_APK_CERTIFICATE_DIGEST: SHA256 hex of the Google APK Certificate
- DREIATTEST_PLUGINS: List of classes implementing `BasePlugin` - gives you the option to handle extra verification
- DREIATTEST_BYPASS_SECRET: **DANGERZONE** If this is set and DREIATTEST_BYPASS_HEADER is sent by the client, the veirification is skipped.
You can find the default value (if any) for each of them in the [settings.py](https://github.com/dreipol/django-dreiattest/blob/master/dreiattest/settings.py)
## Usage
All that's left is to add the `signature_required` view decorator.
```python
from dreiattest.decorators import signature_required
@signature_required()
def demo(request: WSGIRequest):
return JsonResponse({'foo': 'bar'})
```
## Error Handling
The main two exceptions that should be handled by you are `PyAttestException` and `DreiAttestException`. dreiattest ships with the `HandleDreiattestExceptionsMiddleware` you could use if you don't want to handle those errors by yourself. The middleware only catches those two exception classes and returns a `JsonResponse` with status code 400.
```
MIDDLEWARE = [
...
'dreiattest.middlewares.HandleDreiattestExceptionsMiddleware',
]
```
## Typical Flow
1. CLIENT (could be android or google) makes a request to dreiattest/nonce with a device session identifier to obtain a server nonce. The session id as well as the nonce are persisted on the server.
2. CLIENT sends an attestation to dreiattest/key. This request again holds the device session identifier as well as the nonce from step 1. The nonce will be marked as "used" and used to verify the attestation. The public key from the client is then assigned to the device session and also persisted in the database.
3. CLIENT sends a request to any view decorated with `@signature_required`. The request holds an assertion which will be verified before the actual django view is executed.
## Publishing / Contributing
- Create a branch from `master` for possible pull requests
- To publish a new version to pypi:
- Update the version in `__version__.py`
- Trigger `$ pipenv run upload` - This will automatically create and push the correct tag in git and upload that version to pypi
%package -n python3-django-dreiattest
Summary: please add a summary manually as the author left a blank one
Provides: python-django-dreiattest
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-django-dreiattest
# django-dreiattest
dreiattest leverages [pyttest](https://github.com/dreipol/pyattest) and integrates it into django. It handles routing, different config options and persistence of tokens and public keys. To use dreiAttest you need to use the corresponing libraries for [iOS](https://github.com/dreipol/dreiAttest-ios) and [Android / Kotlin Multiplatform](https://github.com/dreipol/dreiAttest-android).
## Installation
dreiAttest is available on PyPI and can be installed via `$ python -m pip install dreiattest-django`.
After the installation make sure to add `dreiattest` to your `INSTALLED_APPS` and trigger all migrations
with `python manage.py migrate dreiattest`. Also, you need to register the default endpoints in your urls.py
```
urlpatterns = [
path('admin/', admin.site.urls),
path('', include('dreiattest.urls')),
...
]
```
## Config
There are multiple settings you can and or have to set in your settings.py. The following are mandatory:
- **Apple**: `DREIATTEST_APPLE_APPID`
- **Google (Legacy: Safety Net)**: `DREIATTEST_GOOGLE_APK_NAME`, `DREIATTEST_GOOGLE_APK_CERTIFICATE_DIGEST`
- **Google Play Integrity API**: `DREIATTEST_GOOGLE_APK_NAME`, `DREIATTEST_GOOGLE_DECRYPTION_KEY`, `DREIATTEST_GOOGLE_VERIFICATION_KEY`
These are all the possible config values and what they do.
- DREIATTEST_BASE_URL: Our different endpoints like /key and /nonce will be bellow this slug
- DREIATTEST_UID_HEADER: Header containing the DeviceSession uid
- DREIATTEST_ASSERTION_HEADER: Header containing the assertion
- DREIATTEST_USER_HEADERS_HEADER: Header containing the list of comma separated headers that are included in the assertion
- DREIATTEST_NONCE_HEADER: Header containing the server nonce that was used inside the attestation
- DREIATTEST_BYPASS_HEADER: Header containing the shared secret to bypass the verification process. Helpfull for debugging
- DREIATTEST_APPLE_APPID: Header containing the apple app id
- DREIATTEST_GOOGLE_APK_NAME: Header containing the google apk name
- DREIATTEST_GOOGLE_DECRYPTION_KEY: A Base64 encoded AES key secret as described [here](https://developer.android.com/google/play/integrity/verdict#decrypt-verify)
- DREIATTEST_GOOGLE_VERIFICATION_KEY: A Base64 encoded public key as described [here](https://developer.android.com/google/play/integrity/verdict#decrypt-verify)
- DREIATTEST_PRODUCTION: Indicating if we're in a production environment or not. Some extra verifications are made if this is true. Those are described in the [pyttest](https://github.com/dreipol/pyattest) readme.
- DREIATTEST_GOOGLE_APK_CERTIFICATE_DIGEST: SHA256 hex of the Google APK Certificate
- DREIATTEST_PLUGINS: List of classes implementing `BasePlugin` - gives you the option to handle extra verification
- DREIATTEST_BYPASS_SECRET: **DANGERZONE** If this is set and DREIATTEST_BYPASS_HEADER is sent by the client, the veirification is skipped.
You can find the default value (if any) for each of them in the [settings.py](https://github.com/dreipol/django-dreiattest/blob/master/dreiattest/settings.py)
## Usage
All that's left is to add the `signature_required` view decorator.
```python
from dreiattest.decorators import signature_required
@signature_required()
def demo(request: WSGIRequest):
return JsonResponse({'foo': 'bar'})
```
## Error Handling
The main two exceptions that should be handled by you are `PyAttestException` and `DreiAttestException`. dreiattest ships with the `HandleDreiattestExceptionsMiddleware` you could use if you don't want to handle those errors by yourself. The middleware only catches those two exception classes and returns a `JsonResponse` with status code 400.
```
MIDDLEWARE = [
...
'dreiattest.middlewares.HandleDreiattestExceptionsMiddleware',
]
```
## Typical Flow
1. CLIENT (could be android or google) makes a request to dreiattest/nonce with a device session identifier to obtain a server nonce. The session id as well as the nonce are persisted on the server.
2. CLIENT sends an attestation to dreiattest/key. This request again holds the device session identifier as well as the nonce from step 1. The nonce will be marked as "used" and used to verify the attestation. The public key from the client is then assigned to the device session and also persisted in the database.
3. CLIENT sends a request to any view decorated with `@signature_required`. The request holds an assertion which will be verified before the actual django view is executed.
## Publishing / Contributing
- Create a branch from `master` for possible pull requests
- To publish a new version to pypi:
- Update the version in `__version__.py`
- Trigger `$ pipenv run upload` - This will automatically create and push the correct tag in git and upload that version to pypi
%package help
Summary: Development documents and examples for django-dreiattest
Provides: python3-django-dreiattest-doc
%description help
# django-dreiattest
dreiattest leverages [pyttest](https://github.com/dreipol/pyattest) and integrates it into django. It handles routing, different config options and persistence of tokens and public keys. To use dreiAttest you need to use the corresponing libraries for [iOS](https://github.com/dreipol/dreiAttest-ios) and [Android / Kotlin Multiplatform](https://github.com/dreipol/dreiAttest-android).
## Installation
dreiAttest is available on PyPI and can be installed via `$ python -m pip install dreiattest-django`.
After the installation make sure to add `dreiattest` to your `INSTALLED_APPS` and trigger all migrations
with `python manage.py migrate dreiattest`. Also, you need to register the default endpoints in your urls.py
```
urlpatterns = [
path('admin/', admin.site.urls),
path('', include('dreiattest.urls')),
...
]
```
## Config
There are multiple settings you can and or have to set in your settings.py. The following are mandatory:
- **Apple**: `DREIATTEST_APPLE_APPID`
- **Google (Legacy: Safety Net)**: `DREIATTEST_GOOGLE_APK_NAME`, `DREIATTEST_GOOGLE_APK_CERTIFICATE_DIGEST`
- **Google Play Integrity API**: `DREIATTEST_GOOGLE_APK_NAME`, `DREIATTEST_GOOGLE_DECRYPTION_KEY`, `DREIATTEST_GOOGLE_VERIFICATION_KEY`
These are all the possible config values and what they do.
- DREIATTEST_BASE_URL: Our different endpoints like /key and /nonce will be bellow this slug
- DREIATTEST_UID_HEADER: Header containing the DeviceSession uid
- DREIATTEST_ASSERTION_HEADER: Header containing the assertion
- DREIATTEST_USER_HEADERS_HEADER: Header containing the list of comma separated headers that are included in the assertion
- DREIATTEST_NONCE_HEADER: Header containing the server nonce that was used inside the attestation
- DREIATTEST_BYPASS_HEADER: Header containing the shared secret to bypass the verification process. Helpfull for debugging
- DREIATTEST_APPLE_APPID: Header containing the apple app id
- DREIATTEST_GOOGLE_APK_NAME: Header containing the google apk name
- DREIATTEST_GOOGLE_DECRYPTION_KEY: A Base64 encoded AES key secret as described [here](https://developer.android.com/google/play/integrity/verdict#decrypt-verify)
- DREIATTEST_GOOGLE_VERIFICATION_KEY: A Base64 encoded public key as described [here](https://developer.android.com/google/play/integrity/verdict#decrypt-verify)
- DREIATTEST_PRODUCTION: Indicating if we're in a production environment or not. Some extra verifications are made if this is true. Those are described in the [pyttest](https://github.com/dreipol/pyattest) readme.
- DREIATTEST_GOOGLE_APK_CERTIFICATE_DIGEST: SHA256 hex of the Google APK Certificate
- DREIATTEST_PLUGINS: List of classes implementing `BasePlugin` - gives you the option to handle extra verification
- DREIATTEST_BYPASS_SECRET: **DANGERZONE** If this is set and DREIATTEST_BYPASS_HEADER is sent by the client, the veirification is skipped.
You can find the default value (if any) for each of them in the [settings.py](https://github.com/dreipol/django-dreiattest/blob/master/dreiattest/settings.py)
## Usage
All that's left is to add the `signature_required` view decorator.
```python
from dreiattest.decorators import signature_required
@signature_required()
def demo(request: WSGIRequest):
return JsonResponse({'foo': 'bar'})
```
## Error Handling
The main two exceptions that should be handled by you are `PyAttestException` and `DreiAttestException`. dreiattest ships with the `HandleDreiattestExceptionsMiddleware` you could use if you don't want to handle those errors by yourself. The middleware only catches those two exception classes and returns a `JsonResponse` with status code 400.
```
MIDDLEWARE = [
...
'dreiattest.middlewares.HandleDreiattestExceptionsMiddleware',
]
```
## Typical Flow
1. CLIENT (could be android or google) makes a request to dreiattest/nonce with a device session identifier to obtain a server nonce. The session id as well as the nonce are persisted on the server.
2. CLIENT sends an attestation to dreiattest/key. This request again holds the device session identifier as well as the nonce from step 1. The nonce will be marked as "used" and used to verify the attestation. The public key from the client is then assigned to the device session and also persisted in the database.
3. CLIENT sends a request to any view decorated with `@signature_required`. The request holds an assertion which will be verified before the actual django view is executed.
## Publishing / Contributing
- Create a branch from `master` for possible pull requests
- To publish a new version to pypi:
- Update the version in `__version__.py`
- Trigger `$ pipenv run upload` - This will automatically create and push the correct tag in git and upload that version to pypi
%prep
%autosetup -n django-dreiattest-0.0.31
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-django-dreiattest -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Thu May 18 2023 Python_Bot <Python_Bot@openeuler.org> - 0.0.31-1
- Package Spec generated
|
