Archives
Contributors
-
Re: Odoo e2e testing with Cypress.
Nice, we use robotframework.Regards,Jens--Kitti Upariphutthiphong <kittiu@ecosoft.co.th> schrieb am Do. 31. Dez. 2020 um 16:57:Dear community,Just recently, I played around with Cypress e2e testing. https://www.cypress.io/And it looks interesting especially for functional end to end testing. Test script is in JS, but it looks easy enough to apply with Odoo.Anyone have experiences using cypress with Odoo already?Kitti U._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Jens Holze
Geschäftsführer (des besten Teams ever)
bloopark systems GmbH & Co. KG
+49 391 563069-10 
jholze@bloopark.de 
www.bloopark.de 
Beethovenstr. 4, 39106 Magdeburg
by Jens Holze - 06:51 - 1 Jan 2020 -
Re: use "%d" in nginx with "dbfilter_from_header" module
Hi Rémy. this is great. thank you. I wrongly thought that <subdomain> was a predefined nginx variable. So now I could capture and assign the value in the server_name statement and use it in the dbfilter.Cheers.Yves.----- Original message -----From: "Rémy Taymans" <remy@coopiteasy.be>To: Contributors <contributors@odoo-community.org>Subject: Re: use "%d" in nginx with "dbfilter_from_header" moduleDate: Friday, January 01, 2021 12:32Dear Yves, The value of the header X-Odoo-dbfilter should be a regular expression matching your database name. (https://github.com/OCA/server-tools/blob/13.0/dbfilter_from_header/override.py#L20) The match performed by Odoo using the regular expression given in the dbfilter header ignore the url you are using for accessing the odoo instance. Considering that the database is named according to the subdomain, the following nginx config should work : server_name foo.example.org; ... proxy_set_header X-Odoo-dbfilter foo; This will match any database that *begins* with `foo`. If the server_name of your nginx configuration file consist of something like : server_name *.example.org; Then you should consider using a regular expression as a server_name value. With this regular expression, extract the subdomain in a variable that can be used as a value for the proxy header. server_name ~^(?<database>.+)\.example\.org$; ... proxy_set_header X-Odoo-dbfilter $database; To get more info about regular expression in nginx configuration file, see : http://nginx.org/en/docs/http/server_names.html#regex_names I have not tested the code given in this email, so use it with caution. :) Regards, -- Rémy Taymans @ Coop IT Easy +32 493 02 69 85 - <https://github.com/coopiteasy> <https://coopiteasy.be> Quoting Yves Goldberg (2020-12-31 11:02:05) > hi all, > How may I pass the equivalent of "dbfilter = *^%d.**" (odoo conf file option) to a nginx proxy_set_header for dbfilter (using module dbfilter_from_header [1] (odoo 13)? > I tried to use "<subdomain>" or $subdomain in my expression but It doesn't get substituted before being sent to odoo. > i.e. unsuccessfully tried: > proxy_set_header X-Odoo-dbfilter \b(?<subdomain>.*)\b\S+; > proxy_set_header X-Odoo-dbfilter \b(?\<subdomain\>.*)\b\S+; proxy_set_header X-Odoo-dbfilter \b(?\$subdomain.*)\b\S+; proxy_set_header X-Odoo-dbfilter ^%d.*; > > anyone can help? > the use case is that I would like to set this dbfilter for only some defined range of subdomains. > TIA > > -- Yves Goldberg* o doo * | Official Partner - OCA delegate Open Source ERP, CRM & CMS Chat with me [2] T +972 (3) 720 8818* M +972 (55) 966 1405 T +32 (2) 588 2500 None [3] www.ygol.com None [4] None [5] None [6] None [7] --
_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
by Yves Goldberg - 04:35 - 1 Jan 2020 -
Re: use "%d" in nginx with "dbfilter_from_header" module
Dear Yves, The value of the header X-Odoo-dbfilter should be a regular expression matching your database name. (https://github.com/OCA/server-tools/blob/13.0/dbfilter_from_header/override.py#L20) The match performed by Odoo using the regular expression given in the dbfilter header ignore the url you are using for accessing the odoo instance. Considering that the database is named according to the subdomain, the following nginx config should work : server_name foo.example.org; ... proxy_set_header X-Odoo-dbfilter foo; This will match any database that *begins* with `foo`. If the server_name of your nginx configuration file consist of something like : server_name *.example.org; Then you should consider using a regular expression as a server_name value. With this regular expression, extract the subdomain in a variable that can be used as a value for the proxy header. server_name ~^(?<database>.+)\.example\.org$; ... proxy_set_header X-Odoo-dbfilter $database; To get more info about regular expression in nginx configuration file, see : http://nginx.org/en/docs/http/server_names.html#regex_names I have not tested the code given in this email, so use it with caution. :) Regards, -- Rémy Taymans @ Coop IT Easy +32 493 02 69 85 - <https://github.com/coopiteasy> <https://coopiteasy.be> Quoting Yves Goldberg (2020-12-31 11:02:05) > hi all, > How may I pass the equivalent of "dbfilter = *^%d.**" (odoo conf file option) to a nginx proxy_set_header for dbfilter (using module dbfilter_from_header [1] (odoo 13)? > I tried to use "<subdomain>" or $subdomain in my expression but It doesn't get substituted before being sent to odoo. > i.e. unsuccessfully tried: > proxy_set_header X-Odoo-dbfilter \b(?<subdomain>.*)\b\S+; > proxy_set_header X-Odoo-dbfilter \b(?\<subdomain\>.*)\b\S+; proxy_set_header X-Odoo-dbfilter \b(?\$subdomain.*)\b\S+; proxy_set_header X-Odoo-dbfilter ^%d.*; > > anyone can help? > the use case is that I would like to set this dbfilter for only some defined range of subdomains. > TIA > > -- Yves Goldberg* o doo * | Official Partner - OCA delegate Open Source ERP, CRM & CMS Chat with me [2] T +972 (3) 720 8818* M +972 (55) 966 1405 T +32 (2) 588 2500 None [3] www.ygol.com None [4] None [5] None [6] None [7] --
by Rémy Taymans - 11:30 - 1 Jan 2020 -
Re: use "%d" in nginx with "dbfilter_from_header" module
Thanks Bruno. The second one is the one I am using and the 1st one is similar.My question is more about if there is a syntax I could use.Happy new year----- Original message -----From: Bruno Joliveau <bruno.joliveau@numigi.com>To: Contributors <contributors@odoo-community.org>Subject: Re: use "%d" in nginx with "dbfilter_from_header" moduleDate: Thursday, December 31, 2020 18:37I sent my mail too quickly ;-)
Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada
Le jeu. 31 déc. 2020 à 11:30, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :Hi Yves,Maybe this https://github.com/muk-it/muk_base/tree/13.0/muk_dbfilter help you?Have a nice day!Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, CanadaLe jeu. 31 déc. 2020 à 05:02, Yves Goldberg <yves@ygol.com> a écrit :hi all,How may I pass the equivalent of "dbfilter = ^%d.*" (odoo conf file option) to a nginx proxy_set_header for dbfilter (using module dbfilter_from_header (odoo 13)?I tried to use "<subdomain>" or $subdomain in my expression but It doesn't get substituted before being sent to odoo.i.e. unsuccessfully tried:proxy_set_header X-Odoo-dbfilter \b(?<subdomain>.*)\b\S+;proxy_set_header X-Odoo-dbfilter \b(?\<subdomain\>.*)\b\S+;proxy_set_header X-Odoo-dbfilter \b(?\$subdomain.*)\b\S+;proxy_set_header X-Odoo-dbfilter ^%d.*;anyone can help?the use case is that I would like to set this dbfilter for only some defined range of subdomains.TIA--Yves Goldbergodoo| Official Partner - OCA delegateOpen Source ERP, CRM & CMST +972 (3) 720 8818
M +972 (55) 966 1405T +32 (2) 588 2500
--_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe
by Yves Goldberg - 09:11 - 1 Jan 2020 -
Re: use "%d" in nginx with "dbfilter_from_header" module
I sent my mail too quickly ;-)Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada
Le jeu. 31 déc. 2020 à 11:30, Bruno Joliveau <bruno.joliveau@numigi.com> a écrit :Hi Yves,Maybe this https://github.com/muk-it/muk_base/tree/13.0/muk_dbfilter help you?Have a nice day!Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada
Le jeu. 31 déc. 2020 à 05:02, Yves Goldberg <yves@ygol.com> a écrit :hi all,How may I pass the equivalent of "dbfilter = ^%d.*" (odoo conf file option) to a nginx proxy_set_header for dbfilter (using module dbfilter_from_header (odoo 13)?I tried to use "<subdomain>" or $subdomain in my expression but It doesn't get substituted before being sent to odoo.i.e. unsuccessfully tried:proxy_set_header X-Odoo-dbfilter \b(?<subdomain>.*)\b\S+;proxy_set_header X-Odoo-dbfilter \b(?\<subdomain\>.*)\b\S+;proxy_set_header X-Odoo-dbfilter \b(?\$subdomain.*)\b\S+;proxy_set_header X-Odoo-dbfilter ^%d.*;anyone can help?the use case is that I would like to set this dbfilter for only some defined range of subdomains.TIA--Yves Goldbergodoo| Official Partner - OCA delegateOpen Source ERP, CRM & CMST +972 (3) 720 8818
M +972 (55) 966 1405T +32 (2) 588 2500 --_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Bruno Joliveau - 05:36 - 31 Dec 2020 -
Re: use "%d" in nginx with "dbfilter_from_header" module
Hi Yves,Maybe this https://github.com/muk-it/muk_base/tree/13.0/muk_dbfilter help you?Have a nice day!Bruno Joliveau - Architecte applications - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada
Le jeu. 31 déc. 2020 à 05:02, Yves Goldberg <yves@ygol.com> a écrit :hi all,How may I pass the equivalent of "dbfilter = ^%d.*" (odoo conf file option) to a nginx proxy_set_header for dbfilter (using module dbfilter_from_header (odoo 13)?I tried to use "<subdomain>" or $subdomain in my expression but It doesn't get substituted before being sent to odoo.i.e. unsuccessfully tried:proxy_set_header X-Odoo-dbfilter \b(?<subdomain>.*)\b\S+;proxy_set_header X-Odoo-dbfilter \b(?\<subdomain\>.*)\b\S+;proxy_set_header X-Odoo-dbfilter \b(?\$subdomain.*)\b\S+;proxy_set_header X-Odoo-dbfilter ^%d.*;anyone can help?the use case is that I would like to set this dbfilter for only some defined range of subdomains.TIA--Yves Goldbergodoo| Official Partner - OCA delegateOpen Source ERP, CRM & CMST +972 (3) 720 8818
M +972 (55) 966 1405T +32 (2) 588 2500 --_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Bruno Joliveau - 05:36 - 31 Dec 2020 -
Odoo e2e testing with Cypress.
Dear community,Just recently, I played around with Cypress e2e testing. https://www.cypress.io/And it looks interesting especially for functional end to end testing. Test script is in JS, but it looks easy enough to apply with Odoo.Anyone have experiences using cypress with Odoo already?Kitti U.
by Kitti Upariphutthiphong - 04:56 - 31 Dec 2020 -
Re: OCA and security notices
a few considerations,About a 2 years based LTS:yes at Akretion we mostly skipped the uneven Odoo versions since version 8 (before that evolution was so much needed that we couldn't). But that may change. It happens Odoo SA screwed v9 release badly and so far they screwed no even version. But should they screw v16, we might totally change our "LTS" policy and we have no control over what version Odoo will screw or not. That being said, there is also an OCA effort resonance happening on Odoo uneven releases. Look how many modules every Odoo version has 1 year or 2 years after release and it will be clear that this is not just an Akretion thing. In the future, eventually migrations become simpler and we follow every version, I can not tell you except that this would be the condition.About migration cycles:Even if you go for an uneven LTS strategy, not every company may migrate every 2 years (or less), that is just not true. Large projects may need to invest for 1 full year for the implementation, not sure it's appealing to invest 20% of the implementation cost the next year to migrate immediately. The newer the version you migrate too, the more expensive it will be as you will eventually need to migrate the OCA modules yourself or even dig into the early OpenUpgrade bugs/limitations. A company can have a bad year, the integrator may not be available. The market is growing a lot, lots of new integrators have just not the experience to be able to migrate 1 or 2 years after they started their 1st projects where they likely did a lot of shit...As soon as you admit this, having secure versions for only 3 years before being forced to migrate is not appealing at all. I think 4 years (2 LTS cycles) would be a wiser stance.A business opportunity for the OCA?Since Odoo SA says they take care of security for only 3 years, eventually this gives room for the OCA to brag "the OCA ensures the security patches from recent Odoo releases are backported for 4 or 5 years". We may not promise it's all secure, but IMHO promising this backport is cheap and may drive more audiences to the OCA.About Odoo SA trying to please the VCs.It has been very true in the past and eventually shaped the released cycle. But we know it's no longer true: despite nearly losing control to the VCs back in 2015 (as Fabien admits himself that had only 2 month of cash if they didn't made the last VC round where they had to change the license and start doing proprietary code), they now managed to get totally independent from them again. Eventually we were pissed of by the risk taken while we didn't choose open source for that kind of risk. But it's over now. That being said, Odoo SA is now a company with many salesmen and managers, sort of unproductive people and consequently they need to sell new projects like mad to feed everybody. So eventually they are structurally doomed to keep riding the rocket.About security and Python versions:again IMHO the OCA is not wise when it follows Odoo SA Python version policy, like have the v14 CI run Python 3.6 (end of life next year). Because what we see with the Odoo CVE also just happens in the Python packages we depend on. In new fields like web, API connectors, ecommerce, SOAP... Python packages come and go, replaced by newer technologies. Newer packages use recent Python versions and loose compatibility with older Pythons. Hence if you use an old Python, chances are your Python packages have much more CVE that will not get fixed, not even for a newer Python (a new lib might be used instead). IMHO, Odoo SA supports older Pythons by accident because they come from legacy, But just because they support it by accident is not a good reason for the OCA to align to this policy. We don't run the CI on windows just because Odoo SA also make Odoo instalable on Windows, right? So why cannot we say: "you want Odoo 14? The OCA CI ensures it works on Python 3.7+, so evolve your distro before starting your real life project, doing that may give you 1 extra year of CVE free packages in the future."About web enabled ERP and security:We have to face it: how many not up to date Odoo ecommerces and portals are there around in the wild? Now think about how easy it is to take the CVE list of Odoo and of its old Python dependencies and scan the web to attack these older Odoos? Think how hard it is to migrate and how naive were some companies to do an Odoo ecommerce before understanding this. Think if company X has an unfair competitor Y ready to pay a hacker to use these CVE to attack the old Odoo, think how easy it is to take over the company X data or even spoil its ERP... At Akretion this is the kind of reasoning we had before building Shopinvader for instance.Regards.On Thu, Dec 31, 2020 at 11:12 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:For me the path is clear: upgrade to the latest possible Odoo version, and that's why OpenUpgrade is done and funded by OCA itself, and the most famous OCA modules are migrated to all versions by regular contributors.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ValyiFounder and consultant
by "Raphaël Valyi" <rvalyi@akretion.com> - 04:06 - 31 Dec 2020 -
Re: OCA and security notices
For me the path is clear: upgrade to the latest possible Odoo version, and that's why OpenUpgrade is done and funded by OCA itself, and the most famous OCA modules are migrated to all versions by regular contributors.Regards.
by Pedro M. Baeza - 03:11 - 31 Dec 2020 -
Re: OCA and security notices
Hi Tom, at least i heard the same about other partners treating the even versions as innovative and the uneven as stabilizing. At initOS we pretty much do the same. To me even 2 years cyles seem somewhat odd in an ERP world. I personally think Odoo constantly tries to dance on several weddings. One of them is the VC that requires "measurable" process, the other general Marketing conduct (you always have to have news to sell / upsell) and than of course the underlying drag of community features into enterprise (and back ;-)). I'd personally recommend trying to optimize for a two year cycle but i am not really in favour of name that LTS, simply because that would again be a matter of discussion within the OCA and especially in the already difficult communication with Odoo S.A. So in short treating even versions as somewhat LTS (without naming it like that) is reasonable and probably a good strategy. For OpenUpgrade however we need to cover the uneven version in the same manner Best and happy new year in advance Frederik Am Donnerstag, den 31.12.2020, 13:56 +0000 schrieb Tom: > Odoo is not taking any responsibility for fixing security issues on > older versions. Since OCA is understaffed, it's hard to keep all > balls in the air: maintaining and bugfixing older modules, doing > security patches in OCB, maintaining OpenUpgrade, etc. > > I heard that Akretion is skipping the uneven versions of Odoo, but > maybe I heard wrong. > > Would it be a good idea to take the initiative to designate certain > versions as "LTS" releases, making sure that these have security > patches, bugfixes and an upgrade path? Similar to eg. Django or Linux > Mint. It might serve to bring more focus into a scattered (but > wonderful) open source effort. > > > Dec 23, 2020 11:47:43 Houssine BAKKALI <houssine@coopiteasy.be>: > > > Hi community, > > > > Yesterday a security notices has been published. > > > > Stefan has begun to bring one security fix to OCB with this PR > > > > It raises what seems to be an important point about the handling of > > the security fixes for the unsupported Odoo version on OCB. Will > > this should be taken in charge by OCA, as OCB is under OCA umbrella > > or it'll remain on the goodwill of the community's members ? I > > don't have any problem with one of the possible responses. > > > > My point is how do we takle the minimum about this topic. I mean > > how do we organize the contribution members on this topics ? > > > > My first idea will be to open an issue on OCB for each security > > notice and organize the work as it done for modules migration. What > > do you think ? Creating a PSC team security could be another idea. > > > > Finding the security issues seems to be easy but at this point we > > don't have a tracking on the ones that are brought back on the > > unsupported version on OCB. > > > > Here at Coop IT Easy we'll probably focus on the versions affecting > > our customers it means 9.0 as 11.0 and later are still supported. > > > > Regards, > > > > Housine > > > > > > Virus-free. www.avast.com > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 > > Post to: mailto:contributors@odoo-community.org > > Unsubscribe: https://odoo-community.org/groups?unsubscribe > > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 03:11 - 31 Dec 2020 -
Re: OCA and security notices
Odoo is not taking any responsibility for fixing security issues on older versions. Since OCA is understaffed, it's hard to keep all balls in the air: maintaining and bugfixing older modules, doing security patches in OCB, maintaining OpenUpgrade, etc.
I heard that Akretion is skipping the uneven versions of Odoo, but maybe I heard wrong.
Would it be a good idea to take the initiative to designate certain versions as "LTS" releases, making sure that these have security patches, bugfixes and an upgrade path? Similar to eg. Django or Linux Mint. It might serve to bring more focus into a scattered (but wonderful) open source effort.
Dec 23, 2020 11:47:43 Houssine BAKKALI <houssine@coopiteasy.be>:
Hi community,
Yesterday a security notices has been published.
Stefan has begun to bring one security fix to OCB with this PR
It raises what seems to be an important point about the handling of the security fixes for the unsupported Odoo version on OCB. Will this should be taken in charge by OCA, as OCB is under OCA umbrella or it'll remain on the goodwill of the community's members ? I don't have any problem with one of the possible responses.
My point is how do we takle the minimum about this topic. I mean how do we organize the contribution members on this topics ?
My first idea will be to open an issue on OCB for each security notice and organize the work as it done for modules migration. What do you think ? Creating a PSC team security could be another idea.
Finding the security issues seems to be easy but at this point we don't have a tracking on the ones that are brought back on the unsupported version on OCB.
Here at Coop IT Easy we'll probably focus on the versions affecting our customers it means 9.0 as 11.0 and later are still supported.
Regards,
Housine
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 02:56 - 31 Dec 2020 -
use "%d" in nginx with "dbfilter_from_header" module
hi all,How may I pass the equivalent of "dbfilter = ^%d.*" (odoo conf file option) to a nginx proxy_set_header for dbfilter (using module dbfilter_from_header (odoo 13)?I tried to use "<subdomain>" or $subdomain in my expression but It doesn't get substituted before being sent to odoo.i.e. unsuccessfully tried:proxy_set_header X-Odoo-dbfilter \b(?<subdomain>.*)\b\S+;proxy_set_header X-Odoo-dbfilter \b(?\<subdomain\>.*)\b\S+;proxy_set_header X-Odoo-dbfilter \b(?\$subdomain.*)\b\S+;proxy_set_header X-Odoo-dbfilter ^%d.*;anyone can help?the use case is that I would like to set this dbfilter for only some defined range of subdomains.TIA--Yves Goldbergodoo| Official Partner - OCA delegateOpen Source ERP, CRM & CMST +972 (3) 720 8818
M +972 (55) 966 1405T +32 (2) 588 2500 --
by Yves Goldberg - 11:00 - 31 Dec 2020 -
Re: Mailing list IoT PSC
Hi Stéphane,
I would recommend using GitHub discussions but discord is fine. I'm going to try it.
Thank you !El lun, 28 dic 2020 a las 16:37, Stéphane Bidoul (<stephane.bidoul@acsone.eu>) escribió:Hello Juan,I would recommend using the contributors mailing list first, as it has relatively low traffic.I've also created an #iot channel in discord.We could also create a dedicated mailing list but the risk is it will have little visibility and you may not reach the intended audience.GitHub discussions is worth considering, although there is the risk of dispersing the information and diluting the audience if we have too many communication channels.-sbiOn Thu, Dec 24, 2020 at 4:11 AM Juan DCG <juandcg314@gmail.com> wrote:Hi community,Are there any mailing list of IoT PSC ?Or we can use the new discussions feature of github ?Thanks,Juan._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Juan Del Castillo Gómez - 06:45 - 28 Dec 2020 -
Re: Mailing list IoT PSC
Hello Juan,I would recommend using the contributors mailing list first, as it has relatively low traffic.I've also created an #iot channel in discord.We could also create a dedicated mailing list but the risk is it will have little visibility and you may not reach the intended audience.GitHub discussions is worth considering, although there is the risk of dispersing the information and diluting the audience if we have too many communication channels.-sbiOn Thu, Dec 24, 2020 at 4:11 AM Juan DCG <juandcg314@gmail.com> wrote:Hi community,Are there any mailing list of IoT PSC ?Or we can use the new discussions feature of github ?Thanks,Juan._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 04:35 - 28 Dec 2020 -
RE: Mail cc
Hello,
I would recommend as best approach this one: https://github.com/sygel-technology/sy-server-backend/tree/12.0/mail_show_follower
I’m sure Valentin can propose this module to OCA if there is interest.
Regards,
Rafael
De: Sergio Corato <sergiocorato@gmail.com>
Enviado el: martes, 1 de diciembre de 2020 10:47
Para: Contributors <contributors@odoo-community.org>
Asunto: Mail ccHi all,
AFAIK there isn't a generic approach to send mail with CC instead of A, or I miss something?
The use case would be something like: if a mail is sent to 1 recipient, go with A. If there are multiple recipients, 1 go with A and the other with CC.
So an 'integrated' logic, without user intervention (except to optionally change the A recipient, or something other).
Thanks in advance!
Sergio Corato
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rafael Blasco (Moduon) - 10:46 - 27 Dec 2020 -
Re: Module that encrypt printed PDF, which require password to open.
Hello Rafael, something like PKCS is also something some customer is requesting for, but I just don't know how to do. Now I have the weapon :)Thank you everyone,Merry Christmas & Happy New Year.On Wed, Dec 23, 2020 at 6:22 AM Rafael Blasco <rblasco@rbnpro.com> wrote:
Hello,
We have been using from Odoo v8 this one: https://github.com/OCA/reporting-engine/tree/12.0/report_qweb_signer
“sign PDFs using a PKCS#12 certificate” = Encrypt
Regards,
Rafael
De: Enric Tobella [mailto:etobella@creublanca.es]
Enviado el: jueves, 17 de diciembre de 2020 15:17
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Module that encrypt printed PDF, which require password to open.Sure, all yours ;) Keep the commit history and start improving :)
Enric Tobella Alomar
Centros Médicos Creu Blanca
Tel: 902 202 230
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.From: "Kitti Upariphutthiphong" <kittiu@ecosoft.co.th>
To: "Contributors" <contributors@odoo-community.org>
Date: Thu, 17 Dec 2020 12:32:12 -0000
Subject: Re: Module that encrypt printed PDF, which require password to open.
Eric,
Thanks so much. Can I take it to OCA v14? Will be discussing with you along the way. :)
On Thu, 17 Dec 2020, 16:52 Enric Tobella, <etobella@creublanca.es> wrote:
I found the module I did that allows to set the password when generating the file.
Enric Tobella Alomar
Centros Médicos Creu Blanca
Tel: 902 202 230
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.From: Jordi Ballester Alomar <jordi.ballester@forgeflow.com>
To: "Odoo Community Association (OCA) Contributors" <contributors@odoo-community.org>, Enric Tobella <etobella@creublanca.es>
Date: Thu, 17 Dec 2020 10:42:52 +0100
Subject: Re: Module that encrypt printed PDF, which require password to open.
@Enric Tobella you did sonething, did you?
El jue., 17 dic. 2020 10:22, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> escribió:
Dear community,
May I check if anyone had done something already about encrypt printed PDF, which require password to open the file.
Thank you,
Kitti U.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Kitti Upariphutthiphong - 04:45 - 24 Dec 2020 -
Mailing list IoT PSC
Hi community,Are there any mailing list of IoT PSC ?Or we can use the new discussions feature of github ?Thanks,Juan.
by Juan Del Castillo Gómez - 04:11 - 24 Dec 2020 -
Re: OCA and security notices
+1 PSC SecDevOps Team.Hi community,I've a Bachelor in Telecommunications Engineering and a Master in Cybersecurity.I've the mindset for work on security related stuff.Professionally I've a few experience as a SOC engineer and as a SecDevOps Architecture engineer.I already have the background and I have know how implement it strategically, so I could be member of the possible PSC SeDevOps, but actually, I'm retired from Cybersecurity.Due to no email list neither PSC discussion team, I'm going to give you ideas about how security should be implemented, the S-SDLC, in this mail.Security is transversal, we could have a Continious Pentesting against stage environments for preventive bugs on code before production. But is better avoid bug of code at the root.The first concept is move security to developers to be ideally preventive. So, is the developer mindset who capture the flags at design features level and with BDD, TDD apply to security development. Then, integrate it in CI/CD(DevOps), so at the point of view of a threat modelling, security is by design and by default, at the early stage of design, for that, Sec is before than DevOps, so I propose a SecDevOps Team, because is moving security to the left.I search a few to give you orientation guidelines to discuss about:Regards,Juan.El mié, 23 dic 2020 a las 11:17, Florent Cayré (<florent@commown.fr>) escribió:
+1 for a PSC security team who would discuss with Odoo SA so that the team has the time to backport security fixes before the disclosure. Security reports may come from community members after all, why not let the community benefit from this work? Le 23/12/2020 à 11:47, Houssine BAKKALI a écrit : > My first idea will be to open an issue on OCB for each security notice > and organize the work as it done for modules migration. What do you > think ? Creating a PSC team security could be another idea.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Juan Del Castillo Gómez - 11:46 - 23 Dec 2020 -
Re: OCA and security notices
+1 for a PSC security team who would discuss with Odoo SA so that the team has the time to backport security fixes before the disclosure. Security reports may come from community members after all, why not let the community benefit from this work? Le 23/12/2020 à 11:47, Houssine BAKKALI a écrit : > My first idea will be to open an issue on OCB for each security notice > and organize the work as it done for modules migration. What do you > think ? Creating a PSC team security could be another idea.
by Florent Cayré - 12:16 - 23 Dec 2020 -
OCA and security notices
Hi community,
Yesterday a security notices has been published.
Stefan has begun to bring one security fix to OCB with this PR
It raises what seems to be an important point about the handling of the security fixes for the unsupported Odoo version on OCB. Will this should be taken in charge by OCA, as OCB is under OCA umbrella or it'll remain on the goodwill of the community's members ? I don't have any problem with one of the possible responses.
My point is how do we takle the minimum about this topic. I mean how do we organize the contribution members on this topics ?
My first idea will be to open an issue on OCB for each security notice and organize the work as it done for modules migration. What do you think ? Creating a PSC team security could be another idea.
Finding the security issues seems to be easy but at this point we don't have a tracking on the ones that are brought back on the unsupported version on OCB.
Here at Coop IT Easy we'll probably focus on the versions affecting our customers it means 9.0 as 11.0 and later are still supported.
Regards,
Housine
by Houssine BAKKALI - 11:46 - 23 Dec 2020
