keychain | Bash script to access the osx keychain | Script Programming library

I’m working on boost::beast based application on macOS platform, and I wonder how I can provide a client-side certificate to authenticate against the server ?

basically , in macOS the certificates are stored in keychain, and cannot be exported (backed by dedicated hardware called secured-enclave for better security)…

So I wonder if there’s any callback suitable to sign server’s challenge manually with native macOS native code that send the challenge to the keychain/secure-enclave for signing.

basically, I'm looking for a callback that have roughly the following signature :

How can I force VS Code to ask for my macOS Keychain password before each push to GitHub?

VS Code never asked for my GitHub password (via Keychain) until I pushed to GitHub and it asked before each push again.

This was working until a few hours ago when I had some issues and revoked my access and VS Code requested a new token.

Now VS Code does not ask at all for a password. Even when I remove VS Code from the Keychain whitelist, it asks for my password at program start only once and then not again, even not for pushes.

I want VS Code to request my GitHub token before each push from Keychain again.

I have a react-native project. After the bitnary (jcenter) shutted down I started to replace it. Currently I'm using mavenCentral(). Also I'm using the react-native-intercom (wrapper for intercom). When I'm trying to build gradlew assembleRelease. Its throws me an error.

I have recently created an Apple Push Service certificate on my M1 mac mini. In the Keychain, it says the certificate is not trusted.

I have installed the Developer Relations Intermediate Certificate as mentioned in here

Also installed the following Intermediate Certificates from Apple

Still, the Push Service certificate shows it's not trusted. Meanwhile, new development and distribution certificates created are marked as "This certificate is valid". Can anyone point me in the right direction to fix this issue?

I'm trying to run a unit test in GitHub actions before deploying my AWS Lambda, where I'm running Selenium Webdriver with a functioning Selenium-chromium lambda layer (https://github.com/vittorio-nardone/selenium-chromium-lambda). I'm running my environment in Python 3.6 and using ChromeDriver version 95.0.4638.54

I kept on encountering this error upon running the unit test:

I'm having a strange issue where I really cannot find a solution. My production website needs some testing and of course bot checking is enabled (not naming it).

Under my tests after using "Page.addScriptToEvaluateOnNewDocument", the result is not what I would expect.

• If I visit the website directly in the current tab of Chromium, it won't pass the bot checks.
• If I manually open a new tab and visit the website, it passes the bot checks.

At first I thought the scripts are not being executed in the current tab, however checking things that I overwrite shows that they are.

Using this little script I've taken from puppeteer is a PASS in both tabs:

I'm having an issue why trying to build a KMM project using a Jenkins pipeline and fastlane for the iOS part.

Kotlin version: 1.5.31
XCode version: 13.1
Fastlane version: 2.198.1
Ruby version: 2.6.3p62

When executing these steps locally it breaks as well. The Error that fastlane throws is import shared: no such module 'shared'

I figured out that if you run pod install && fastlane xcode_build the build brakes, but if you repeat it a second time it succeeds and creates the project.app file in the DerivedData folder of XCode.

The Jenkinsfile is working correctly on another iOS project which is not a KMM one.

Here is the Jenkinsfile

when I using fastlane to publish ios app in github:

App doesn't run on IOS simulators or building archive but runs on devices. It used to run fine, suddenly (can't pinpoint what is currently different that could cause this) a similar issue happened on android with the File name is too long error after multiple flutter cleans, removing all caches it worked on a real device then on the simulators again, doesn't work for IOS though.

Error message