Minor improvements to HTTPS handling in Agama's web server#1228
Minor improvements to HTTPS handling in Agama's web server#1228
Conversation
imobachgs
left a comment
There was a problem hiding this comment.
In general it looks good (and even better when you fix the conflict) :-) And, please, update the PR's description.
8718d53 to
036f41d
Compare
5ca6a82 to
ac4beba
Compare
imobachgs
left a comment
There was a problem hiding this comment.
IMHO the code looks much better now. Just a few comments, but nothing really relevant. Nice work! Thanks!
| builder.append_extension( | ||
| SubjectAlternativeName::new() | ||
| // use the default Agama host name | ||
| // TODO: use the gethostname crate and use the current real hostname |
There was a problem hiding this comment.
well it partly is : https://github.com/openSUSE/agama/pull/1228/files#diff-280a7d38feb9a8c0c477b0903c149026ea053d231fa7ebe1326b4fd76eec07ecR62
may be @lslezak can say something about this ?
08e4e68 to
6d1d137
Compare
imobachgs
left a comment
There was a problem hiding this comment.
Sorry, but I still see changes in the Gemfile.lock file.
sorry ... found one more commit which contained it ... eliminated. |
|
Oh, it looks like @joseivanlopez was faster and now you have a conflict to solve ;-) |
no problem ... just another small point into work stats ;-) |
Prepare for releasing Agama 9. It includes the following pull requests: - #1101 - #1202 - #1228 - #1231 - #1236 - #1238 - #1239 - #1240 - #1242 - #1243 - #1244 - #1245 - #1246 - #1247 - #1248 - #1249 - #1250 - #1251 - #1252 - #1253 - #1254 - #1255 - #1256 - #1257 - #1258 - #1259 - #1260 - #1261 - #1264 - #1265 - #1267 - #1268 - #1269 - #1270 - #1271 - #1272 - #1273 - #1274 - #1279 - #1280 - #1284 - #1285 - #1286 - #1287 - #1288 - #1289 - #1290 - #1291 - #1292 - #1293 - #1294 - #1295 - #1296 - #1298 - #1299 - #1300 - #1301 - #1302 - #1303 - #1304 - #1305 - #1306 - #1307 - #1308 - #1309 - #1310 - #1311 - #1312 - #1313 - #1314 - #1315 - #1316 - #1317 - #1318 - #1319 - #1320 - #1321 - #1322 - #1323 - #1324 - #1325 - #1326 - #1328 - #1329 - #1331 - #1332 - #1334 - #1338 - #1340 - #1341 - #1342 - #1343 - #1344 - #1345 - #1348 - #1349 - #1351 - #1352 - #1353 - #1354 - #1355 - #1356 - #1357 - #1358 - #1359 - #1360 - #1361 - #1362 - #1363 - #1365 - #1366 - #1367 - #1368 - #1371 - #1372 - #1374 - #1375 - #1376 - #1379 - #1380 - #1381 - #1383 - #1384 - #1385 - #1386 - #1387 - #1388 - #1389 - #1391 - #1392 - #1394 - #1395 - #1397 - #1398 - #1399 - #1400 - #1403
Problem
Purpose is to make https support more "user" friendly. Currently self-generated certificate contains only a generic name and is generated repeatedly on each start (if needed). Also need of explicit specification of user's own certificate on each (re)start is not much friendly.
Solution
Testing
I (mvidner) have tested manually that the certificate (+key) is saved, and reused on service restart, and contains the host name.
Screenshots