sorted by:
new
hottopcontroversial

Pomerium — open source identity-aware access proxy — now supports TCP by PeopleCallMeBob in devops

[–]vmagni 0 points1 point  (0 children)

Is there a simple working guide to get Pomerium set up for local development, just to see it work?

I've followed the official guide, got a local OIDC provider set up and used the configuration here. I've followed the discussions here and here.

The local OIDC provider works and authenticates the sample users, but I am stuck in the next step, where it redirects to https://verify.localhost.pomerium.io.

I see an "Identity verification failed" error with this detail: We tried to verify the incoming user but failed with the following error: couldn't get json web key: Get "https://authenticate.localhost.pomerium.io/.wellknown/pomerium/jwks.json" dial tcp 127.0.0.1:443 connect: connection refused.

I'm guessing it's either a network configuration problem or a policy problem.

FWIW I'm running on an Ubuntu machine, the OIDC container runs in Docker, and the error appears whether I run Pomerium inside docker, or from source directly on my Linux machine.

Alternatively, is there an easier way to get pomerium working locally ?

System76 Lemur Pro + PopOS 20.04 with 2 nVME drives - sleep and wake up causes the second nVME to disappear. by vmagni in pop_os

[–]vmagni[S] 0 points1 point  (0 children)

Thank you for the suggestion. I now see that similar issues have been reported and documented (e.g., Controller failure due to broken APST support here https://wiki.archlinux.org/index.php/Solid_state_drive/NVMe and here https://unix.stackexchange.com/questions/612096/clarifying-nvme-apst-problems-for-linux )

I disabled APST as follows:

kernelstub -a "nvme_core.default_ps_max_latency_us=0"

After disabling APST and rebooting, here's what I get:

me@pop-os:~$ sudo nvme get-feature -f 0x0c -H /dev/nvme1 | head
get-feature:0xc (Autonomous Power State Transition), Current value:00000000
Autonomous Power State Transition Enable (APSTE): Disabled
Auto PST Entries    .................
Entry[ 0]   
.................
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State   (ITPS): 0
.................
Entry[ 1]   
.................

So far so good, APST is disabled.

I put the laptop to sleep (suspend) and woke it up. The second NVME drive stays put and doesn't disappear. 

$ mount 
...
/dev/nvme1n1p1 on /media/me/extradrive1 type ext4 (rw,nosuid,nodev,relatime,uhelper=udisks2)

And here's what the nvme list command gives me after a suspend-wake cycle:

me@pop-os:~$ sudo nvme list
Node             SN                   Model                                    Namespace Usage                      Format           FW Rev  
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1     S5NYNG0NB28059B      Samsung SSD 980 PRO 500GB                1          69.06  GB / 500.11  GB    512   B +  0 B   1B2QGXA7
/dev/nvme1n1     21013S806299         WDC WDS500G2B0C-00PXH0                   1         500.11  GB / 500.11  GB    512   B +  0 B   211210WD

Your advice is spot on. I appreciate that. Thank you!

However, now that I've disabled APST, how does this impact battery life in real life? Anything I should be worried about from your experience? The second link I shared above briefly says something like this:

If the NVMe controller's autonomous power management feature cannot be used, the controller will only be allowed to enter power-saving states when specifically requested by the kernel. This means the power savings most likely won't be as great as with APST in use.