On the App Store of my Macbook Pro, the top buttons are no longer visible

I have a notification that there are updates to install, so as usual, I would like to review them beforehand.

However, when I open the App Store app, I only see the following: App Store with top buttons missing

Normally it would say something like “Featured”, “Installed”, “Updates” and the such. However, now it’s all gone! How can I re-enable the display of the buttons?

How do I store other people’s ssh keys securely?

This is not really a programming question, but please hear me out. I am building a deployment tool, So using my application others can deploy their own application to their own servers. (just like forge.laravel.com),

Following are the use cases for this particular question

  1. I need to store each of my user’s public ssh keys because I need to insert this key in each of the provisioned servers. so that users can log into their servers via ssh without any manual authorizations.
  2. Also, I need to authorize my applications ssh key (ie: my servers public key) into customers servers so that I can execute commands on my user’s server on their behalf.
  3. I need to generate a new key on the newly provisioned customer server and authorize it in github/gitlab of the customer so that when I push/pull from the server I don’t need to enter any username or password.

Coming to the question, Where/how do I store these keys (securely)? can I store them in a specific directory in my server? This makes me think that my server can be a big target for hackers since if they are able to hack, it opens doors to a multitude of servers.

What are the steps I can take to make this setup more secure?

Considering use case 2, does it make any difference if I generate separate keys for separate customers?

How can I safely store application secrets/passwords in git and other version control systems?

When I saw this question: Why is storing passwords in version control a bad idea?

I immediately thought that question could be inverted to be: Why is storing passwords in version control a good idea?

  1. True Infrastructure as Code = App + Config + Secrets, all stored as code. (Having this allows results to be replicated reliably.)
  2. Consistency is the best friend of automation/CI/CD Pipelines. Having App + Config in source control, and Secrets in HashiCorp Vault makes your automation more complex. If all 3 are stored consistently in git automation becomes much easier.
  3. It’s important to store your config in a version control system. The thing is .json or .yaml config files with secrets and other sensitive information embedded alongside the configuration are pretty common. Why not just put those in version control too?
  4. Allowing Secrets in git offers the following benefits:
    1. There’s a changelog of when the secret changed, and an audit trail of who changed it, this knowledge allows the scope of debugging to be narrowed.
    2. Sometimes a dev isn’t sure if their code is wrong, or if the secret is formatted in some weird an unexpected way. A dev being able to look at a dev version of the secret while working, and then an ops person being able to compare a dev and pre-prod version of a secret helps debug quicker. (Example: Maybe a .txt file was created on Mac/Linux by a Dev, then created on Windows by an Ops guy and the dev vs pre-prod version of the secret ended up with 2 separate character encodings?, Missing Quote(s), rn vs m, extra space, all kinds of misspellings.)
    3. I’ve run into a scenario where an app was being rapidly developed, and a new feature required a new secret to be added, the secret was added to the dev environment, then a pre-prod version of the application was launched, it wasn’t working and it took a while to figure out that it was because the newly added secret was never created for (much less applied to) the higher environments. (If secrets were consistently stored in git, this would have been obvious by inspection.)

But then I realized there’s a better question beyond:
Why is storing passwords in version control a bad idea?
vs
Why is storing passwords in version control a good idea?

And that’s:
How can I safely store application secrets/passwords in git?
Challenges:

  • It’s obvious that the secret would need to be stored encrypted. But safely storing encrypted data in git, requires that it’s impossible for decryption keys to be leaked:
    If git users directly decrypt secrets using PGP or symmetric keys, then when the decryption keys get leaked, there’s no way to revoke or invalidate the decryption keys and there’s no way to purge the git history because it’s decentralized.
  • Need a means to audit if a piece of data was decrypted or who decrypted it.
  • Need to be able to assign Granular access rights to who can decrypt what secrets. Devs shouldn’t be able to decrypt prod secrets. Ops person who can decrypt Prod application A’s secrets, shouldn’t necessarily be able to decrypt Prod application B’s secrets.
  • Need to be able to prevent footgun scenarios: like accidentally decrypting a previously encrypted secret, then committing the decrypted version of the secret back to the repo.

I want to download Xcode that I deleted again. But when I open App Store and search for Xcode the download button is grey

When I downloaded it before I did it through App Store but now that doesn’t work because of that the button is grey. Have tried to download Xcode through developer.apple but there it says that I don’t have enough storage which I clearly do because I got 16 GB free. HELP

I want to download Xcode that I deleted again. But when I open App Store and search for Xcode the download button is grey

When I downloaded it before I did it through App Store but now that doesn’t work because of that the button is grey. Have tried to download Xcode through developer.apple but there it says that I don’t have enough storage which I clearly do because I got 16 GB free. HELP

Can a website store data on a browser other than in the following ways

Set up:

Android Mobile device

Firefox Mobile Browser

Last week, I was using a free trial on a certain website, without having logged in, and the way the website kept track seemed to be via cookies. I felt this because :

  1. It would not allow me to access its content in incognito (I’m guessing because then it would not be able to keep track of if I’ve used the free trial or not) and
  2. When I cleared Firefox’s history, cookies, open tabs, etc. I was able to access the free trial again.

However, today, I tried the same thing –

  • Made use of the free trial
  • Cleared previous browser data
  • Tried to re-access the trial

However, this time when I tried to re-access the trial, the website asked me to login.

When I uninstalled and reinstalled Firefox, I was again able to access the free trial the first time, but the second time was asked to login.

Is the website being able to store something persistently on my Firefox app?

Note: This login issue also happened on my desktop (i.e. I was first allowed to access the trial and then was asked to login)

Help please with correct saving multiselect field for Store view edit form

Please help with correct saving adding custom field for Store View edit form. Default Magento Store view edit form: (Stores->All Stores->Any Store) – https://screencast.com/t/WPA3owq3 – https://screencast.com/t/2t3Bg9vYizH0 Here is the way how I have added custom field: using observer (subscribed on the adminhtml_store_edit_form_prepare_form event via adminhtml/events.xml) added field https://screencast.com/t/bUow3hzc73Aq In the admin part new field has been added successfully, BUT I have trouble with multiple values sending (event if I select couple values, anyway magento SENDS ONLY ONE value – https://www.screencast.com/t/GOyaXm1m) Help please, I fighting on this issue more than 2 days already. Maybe anybody knows about any existing restriction for Store View edit form?

Correctly store device info with Redux in React Native app

I’m currently building a React Native application and wondering if storing device information such:

  • if my app has granted location permission
  • location service is turned on
  • last known user location

in the Redux store can be a good idea.
I have different components that needs to know this informations and storing in Redux can grant me a predictable state. In the case, maybe I can store them like this:

{   user: {     id: '123'     name: 'Markus'     ...   },   device: {     locationPermission: 'denied'     locationActive: false     lastKnownLocation: {       lat: 44.123,       lng: 32.123     }   },   ... } 

Are there any cons about this approach?