| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Yogesh Mahajan <yogesh(dot)mahajan(at)enterprisedb(dot)com> |
| Cc: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgAdmin4][Patch]: Fixed default public IP range issue in AWS deployment |
| Date: | 2022-03-11 07:18:22 |
| Message-ID: | CA+OCxoy51HUPUFk9AGo1H4aVJt6dDDA7Pf1gKJkZ7spgXMG4Yg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Fri, 11 Mar 2022 at 03:52, Yogesh Mahajan <
yogesh(dot)mahajan(at)enterprisedb(dot)com> wrote:
> Hi,
>
> Patch looks fine. IP Addresses are prefixed by 32 and 128 for IPv4 and
> IPv6 respectively.
>
I hope you mean suffixed, not prefixed :-)
> Thanks,
> Yogesh Mahajan
> EnterpriseDB
>
>
> On Fri, Mar 11, 2022 at 8:49 AM Khushboo Vashi <
> khushboo(dot)vashi(at)enterprisedb(dot)com> wrote:
>
>> Hi,
>>
>> Please find the attached patch to fix the default Public IP range issue
>> in AWS deployment.
>>
>> @Yogesh Mahajan <yogesh(dot)mahajan(at)enterprisedb(dot)com>, please test.
>>
>>
>> Thanks,
>> Khushboo
>>
> --
--
Dave Page
https://pgsnake.blogspot.com
EDB Postgres
https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Akshay Joshi | 2022-03-11 08:42:48 | Re: [pgAdmin4][Patch]: Fixed default public IP range issue in AWS deployment |
| Previous Message | Khushboo Vashi | 2022-03-11 06:26:25 | Re: [pgAdmin4][Patch]: Fixed default public IP range issue in AWS deployment |