-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use webcals URI scheme when accessing via HTTPS (PFS directive) #748
Comments
PFS = Perfect forward secrecy? |
|
Yeah i meant Perfect forward secrecy. |
Can I please get started with working on this issue? |
Sorry for the stupid question but what are you waiting for (or who's asked)? |
could you please help me get started with the same please :) |
how could I help you? I can partially read PHP but otherwise I'm more of a logic person. |
Like please tell me what file contains the bug :) |
You can just search the code for I‘m not sure whether this issue is in a php or a JavaScript file. |
Ok i searched in the rep for "webcal" and in my browser for "webcal://" But i found something by searching for "subscribe" that is written in php: Lines 12 to 15 in 17e6951
Maybe this is an approach for you. |
cool @Somebodyisnobody I will look into it :) |
@arunikayadav42 do you have news for us? |
"webcalURL" is defined in calendar/controller/viewcontroller.php Line 226 in 28dc8bf
|
I am still looking into the same.Need two more days please due to some technical glitches :) |
Steps to reproduce
Expected behaviour
Nextcloud applies PFS to the webcal-link and forms it into an webcals-link
Actual behaviour
If i access via TLS the subscribtion link is still webcal://
I cannot find an offical URI scheme but all of my clients does support the webcals://-sheme
Some examples:
@georgehrke said in nextcloud/server#8039 (comment)
I tested that with Outlook:
My server is running on TLS at port 444 (DNAT because of internal routes), so my scheme is webcals://my.domain:444/remote.php/dav/.....
So in fact what Georg expects from other webcal clients isn't what other developers think... 😯 😞
Considering the unofficial support of "webcals://" and the Outlook-test it would be appropriate to apply PFS accordingly and use webcals:// when accessing via HTTPS.
Server configuration
Web server: nginx
Database: mysql
PHP version: 7.2
Server version: 13
Calendar version: 1.6.0
Updated from an older installed version or fresh install: updated
Are you using external storage, if yes which one: local
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: newest FF
CalDAV-clients: Thunderbird, WebcalSync, CalDAV and infrequently Outlook
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: