Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
On Thu 27 Oct 2022 at 01:48:44 (+0200), Mario Marietto wrote: > Il giorno gio 27 ott 2022 alle ore 01:01 David Wright ha scritto: > > On Thu 27 Oct 2022 at 00:21:50 (+0200), Mario Marietto wrote: > > > Please,check the images below. The image 1 and 2 come from the kernel > > file > > > unpacked with the cpio command (cpio -idv < initrd.img-5.10.0-18-amd64 -D > > > > > /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64),while > > > on the picture n. 3 You can see all the pictures that are inside the > > kernel > > > file when I have opened it with engrampa. I don't know where the truth > > is. > > > I see only contradictory information. Something is lying : who is ? cpio > > or > > > engrampa ? > > > > > > 1) https://ibb.co/0mCFCW7 > > > 2) https://ibb.co/pjGsTY5 > > > 3) https://ibb.co/k3TMFsk > > > > Have you read https://github.com/mate-desktop/engrampa/issues/191 > > > > You may be working outside the limits of defined behaviour > > when you create .cpio files with duplicate entries. That's > > doesn't make much sense when you intend to distribute the > > product to other people/systems. > > > I don't want to bother you,but did you read my first message ? You replied > only to the second one and I don't know if you have read or understood the > first one. I ask because it seems there may be some other problems > explained there. Do you want to give it a look ? Thank you very much. Well, I've taken another look at your images. I have to guess precisely what they show, as I've never used engrampa. But there's one thing about #3 that I don't like the look of: The window labelled "Posizione:" shows "/usr/share/plymouth/themes/homeworld", but I assume that it refers to what's inside the cpio archive called "initrd.img-5.10.0-18-amd64" highlighted in the window above. If that's a conventional initrd, then I would expect "Posizione:" to show "usr/share/plymouth/themes/homeworld", because I don't recall ever seeing an absolute filename in an initrd. This could lead to your writing to or reading from unexpected places in your filesystem, depending on whoami. (Running these commands as root might perhaps be one reason why you're writing /home/ziomario/… … … almost throughout). That could be a red herring, but unlike mc, which may have to prefix a filename with "/" to show it /is/ a directory, engrampa doesn't need that indication here, because it puts a "/" after homeworld, which shows the same thing. Anyway, contrast: $ find /etc/resolv.conf /etc/networks -print | cpio -ov > /tmp/absolute.cpio /etc/resolv.conf /etc/networks 1 block $ find /etc/resolv.conf /etc/networks -print | cpio -ov --no-absolute-filenames > /tmp/relative.cpio cpio: Removing leading `/' from member names /etc/resolv.conf /etc/networks 1 block $ which list as: $ cpio -t < /tmp/absolute.cpio /etc/resolv.conf /etc/networks 1 block $ cpio -t < /tmp/relative.cpio etc/resolv.conf etc/networks 1 block $ You should be using files that look like relative.cpio. Cheers, David.
Re: Exécuter un fichier exe en ligne de commande
On Wed, 26 Oct 2022, awache...@gmail.com wrote: Il semble que mes mails ne sont plus reçus sur la ML. Les recevez vous ? En tout cas je ne les reçois plusieurs semaines ? Merci A. Valmer You received a reply on 25 October. fjd -- Davis Verbum sat sapienti.
Re: Peculiarities of Toshiba L200 2.5in HDD
On 10/25/22 21:38, Max Nikulin wrote: On 26/10/2022 10:42, David Christensen wrote: P.S. I have not managed to change heads unload timeout for Toshiba L200 using hdparm. In your case due to high G-Sense_Error_Rate increasing timeout might be dangerous. So, you own one of these drives? I have a Toshiba L200 HDWK105 SATA 3 500G CMR disk as a secondary storage. I do not like that heads unload timeout is just a few seconds and such state is hidden, so udisks2 wakes it up every 10 minutes to poll for its SMART state. I see a lot of warnings in docs for HDD tools and I am unsure how to stay on the safe margin during experiments. I do not expect anything directly related to the original subject in this thread, but to not hijack this thread, you may ask your questions e.g. in response to https://lists.debian.org/msgid-search/?m=tbohk8$60u$1...@ciao.gmane.io On 10/26/22 09:27, Max Nikulin wrote: > On 26/10/2022 17:21, Dan Ritter wrote: >> No, no, you have found the most likely problem. > > I expect that David may have some questions concerning this disk series. We need more information from the OP. I am reminded of an electronics story. A rock musician goes into a music shop and buys an amplifier for his electric guitar. He comes back the next day and complains that the amplifier is defective. The salesman tests the amplifier, and sure enough it does not work. The salesman looks inside the back of the head, and notices that some capacitors are missing. The salesman asks the customer to demonstrate how he was using the amplifier. So, the customer turns on the power switch, turns the volume knob up to 10, and plugs in a guitar... David
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
Hello David, I don't want to bother you,but did you read my first message ? You replied only to the second one and I don't know if you have read or understood the first one. I ask because it seems there may be some other problems explained there. Do you want to give it a look ? Thank you very much. Il giorno gio 27 ott 2022 alle ore 01:01 David Wright < deb...@lionunicorn.co.uk> ha scritto: > On Thu 27 Oct 2022 at 00:21:50 (+0200), Mario Marietto wrote: > > Please,check the images below. The image 1 and 2 come from the kernel > file > > unpacked with the cpio command (cpio -idv < initrd.img-5.10.0-18-amd64 -D > > > /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64),while > > on the picture n. 3 You can see all the pictures that are inside the > kernel > > file when I have opened it with engrampa. I don't know where the truth > is. > > I see only contradictory information. Something is lying : who is ? cpio > or > > engrampa ? > > > > 1) https://ibb.co/0mCFCW7 > > 2) https://ibb.co/pjGsTY5 > > 3) https://ibb.co/k3TMFsk > > Have you read https://github.com/mate-desktop/engrampa/issues/191 > > You may be working outside the limits of defined behaviour > when you create .cpio files with duplicate entries. That's > doesn't make much sense when you intend to distribute the > product to other people/systems. > > Cheers, > David. > > -- Mario.
Failure in fuse3 hook prevents initramfs update
I'm trying to do an update to my Debian 11 system, and keep getting the following failure: E: /usr/share/initramfs-tools/hooks/fuse failed with return 1. Trying to get a little more information, I ran update-initramfs -u -v -k all and after many lines of output, got: Adding binary /usr/lib/x86_64-linux-gnu/libe2p.so.2.3 Calling hook fuse Adding binary /sbin/mount.fuse3 E: /usr/share/initramfs-tools/hooks/fuse failed with return 1. I reported this as a bug against fuse3 last Saturday, but to date haven't heard anything from the maintainer. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022252 So... any ideas what's going on? And more importantly what can I do about it?
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
On Thu 27 Oct 2022 at 00:21:50 (+0200), Mario Marietto wrote: > Please,check the images below. The image 1 and 2 come from the kernel file > unpacked with the cpio command (cpio -idv < initrd.img-5.10.0-18-amd64 -D > /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64),while > on the picture n. 3 You can see all the pictures that are inside the kernel > file when I have opened it with engrampa. I don't know where the truth is. > I see only contradictory information. Something is lying : who is ? cpio or > engrampa ? > > 1) https://ibb.co/0mCFCW7 > 2) https://ibb.co/pjGsTY5 > 3) https://ibb.co/k3TMFsk Have you read https://github.com/mate-desktop/engrampa/issues/191 You may be working outside the limits of defined behaviour when you create .cpio files with duplicate entries. That's doesn't make much sense when you intend to distribute the product to other people/systems. Cheers, David.
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
Please,check the images below. The image 1 and 2 come from the kernel file unpacked with the cpio command (cpio -idv < initrd.img-5.10.0-18-amd64 -D /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64),while on the picture n. 3 You can see all the pictures that are inside the kernel file when I have opened it with engrampa. I don't know where the truth is. I see only contradictory information. Something is lying : who is ? cpio or engrampa ? 1) https://ibb.co/0mCFCW7 2) https://ibb.co/pjGsTY5 3) https://ibb.co/k3TMFsk Il giorno mer 26 ott 2022 alle ore 23:04 Mario Marietto < marietto2...@gmail.com> ha scritto: > Hello to everyone. > > I'm trying to understand the reasons why the kernel file that I generate > does not work correctly. Maybe I've understood something,but I don't have a > clear picture of the problem. I want to try to explain what's wrong using > my method of expression because I find it easier. A more "advanced" way may > be able to help you,but it will not help me and the result will be that we > will not understand each other. So. I've created the folder called > "kernels" like this : > > mkdir -p /home/ziomario/Scrivania/PassT-Cubic/kernels/ > > inside of it I have copied the following kernel file : > > initrd.img-5.10.0-18-amd64.gz > > it is unaltered. I haven't added any logos and pictures inside of it. > After this,I have created two more folders : > > mkdir -p /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped > mkdir -p > /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64 > > and then I did : > > cd /home/ziomario/Scrivania/PassT-Cubic/kernels/ > > gunzip -k initrd.img-5.10.0-18-amd64.gz > > cpio -idv < initrd.img-5.10.0-18-amd64 -D > /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64 > > Every time I give the latest command (the cpio one),something odd happens > and I don't understand the reason. Inside the folder > "/usr/share/plymouth/themes/homeworld",two new files are created : > debian.png and logo.png. The first one is correct. I mean,this is one of > the pictures that I want to add inside the kernel file. But the second > file,logo.png is wrong. It is an old picture that I used sometime ago and > that I don't use anymore because I created a new logo. Let's say that the > folder "/usr/share/plymouth" and "/usr/share/plymouth/themes/underworld" > are two folders that I have created on my host os and inside of them I have > stored the correct pictures that I want to add inside the kernel file. > Later in the process,I issue the below commands to copy the correct images > inside the kernel file before re-packing it. > > cp /usr/share/plymouth/debian-logo.png > /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64/usr/share/plymouth/ > > cp /usr/share/plymouth/themes/homeworld/debian.png > /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64/usr/share/plymouth/themes/homeworld > > cp /usr/share/plymouth/themes/homeworld/logo.png > /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64/usr/share/plymouth/themes/homeworld > > At the moment I haven't reached that step because the cpio command (cpio > -idv < initrd.img-5.10.0-18-amd64 -D > /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64) > behavior is not expected. > > Since I'm using unaltered kernel files,I don't know where the cpio command > (cpio -idv < initrd.img-5.10.0-18-amd64 -D > /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64) > gets those images when I run it. And most of all,I don't know why those > pictures are copied inside the folder > "/usr/share/plymouth/themes/underworld",overwriting the already existing > pictures that are already there. As I repeat,those files aren't stored > inside the kernel file (initrd.img-5.10.0-18-amd64),because it is unaltered > and it contains only the default debian pictures,which are different from > mine. I hope that I have been clear. Sorry I don't have another way to > explain what happens other than my narrative. > > Il giorno mar 25 ott 2022 alle ore 22:50 Thomas Schmitt > ha scritto: > >> Hi, >> >> Mario Marietto wrote: >> > You seem to understand well what I'm trying to do and you are >> > able to give good suggestions. >> >> Probably i only have a good run of guessing here. >> >> >> > It seems that there isn't any CPIO >> > parameter that overwrites the old image. Is this correct ? >> >> I am not aware of any. The nature of a sequential archive does not invite >> for random access changes. >> >> >> > I remember that >> > the old method (unpack and repack the files inside the kernel image) >> failed. >> > I'm not able to understand why. >> >> Understanding what special detail spoils this normally well working >> method whould probably be helpful for your goals. You'd have to compare >> what's in a working appended initrd and one that was fres
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
Hello to everyone. I'm trying to understand the reasons why the kernel file that I generate does not work correctly. Maybe I've understood something,but I don't have a clear picture of the problem. I want to try to explain what's wrong using my method of expression because I find it easier. A more "advanced" way may be able to help you,but it will not help me and the result will be that we will not understand each other. So. I've created the folder called "kernels" like this : mkdir -p /home/ziomario/Scrivania/PassT-Cubic/kernels/ inside of it I have copied the following kernel file : initrd.img-5.10.0-18-amd64.gz it is unaltered. I haven't added any logos and pictures inside of it. After this,I have created two more folders : mkdir -p /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped mkdir -p /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64 and then I did : cd /home/ziomario/Scrivania/PassT-Cubic/kernels/ gunzip -k initrd.img-5.10.0-18-amd64.gz cpio -idv < initrd.img-5.10.0-18-amd64 -D /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64 Every time I give the latest command (the cpio one),something odd happens and I don't understand the reason. Inside the folder "/usr/share/plymouth/themes/homeworld",two new files are created : debian.png and logo.png. The first one is correct. I mean,this is one of the pictures that I want to add inside the kernel file. But the second file,logo.png is wrong. It is an old picture that I used sometime ago and that I don't use anymore because I created a new logo. Let's say that the folder "/usr/share/plymouth" and "/usr/share/plymouth/themes/underworld" are two folders that I have created on my host os and inside of them I have stored the correct pictures that I want to add inside the kernel file. Later in the process,I issue the below commands to copy the correct images inside the kernel file before re-packing it. cp /usr/share/plymouth/debian-logo.png /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64/usr/share/plymouth/ cp /usr/share/plymouth/themes/homeworld/debian.png /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64/usr/share/plymouth/themes/homeworld cp /usr/share/plymouth/themes/homeworld/logo.png /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64/usr/share/plymouth/themes/homeworld At the moment I haven't reached that step because the cpio command (cpio -idv < initrd.img-5.10.0-18-amd64 -D /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64) behavior is not expected. Since I'm using unaltered kernel files,I don't know where the cpio command (cpio -idv < initrd.img-5.10.0-18-amd64 -D /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64) gets those images when I run it. And most of all,I don't know why those pictures are copied inside the folder "/usr/share/plymouth/themes/underworld",overwriting the already existing pictures that are already there. As I repeat,those files aren't stored inside the kernel file (initrd.img-5.10.0-18-amd64),because it is unaltered and it contains only the default debian pictures,which are different from mine. I hope that I have been clear. Sorry I don't have another way to explain what happens other than my narrative. Il giorno mar 25 ott 2022 alle ore 22:50 Thomas Schmitt ha scritto: > Hi, > > Mario Marietto wrote: > > You seem to understand well what I'm trying to do and you are > > able to give good suggestions. > > Probably i only have a good run of guessing here. > > > > It seems that there isn't any CPIO > > parameter that overwrites the old image. Is this correct ? > > I am not aware of any. The nature of a sequential archive does not invite > for random access changes. > > > > I remember that > > the old method (unpack and repack the files inside the kernel image) > failed. > > I'm not able to understand why. > > Understanding what special detail spoils this normally well working > method whould probably be helpful for your goals. You'd have to compare > what's in a working appended initrd and one that was freshly packed up > and does not work. (cpio -t > > > mv initrd.img-5.10.0-19-amd64 initrd.img-5.10.0-19-amd64_ > > mv initrd.img-5.10.0-19-amd64 initrd.img-5.10.0-19-amd64- > > find [...] | cpio -ov > ../initrd.img-5.10.0-19-amd64 > > I find your re-usal of that lengthy file name confusing. > Consider to give the various intermediate archives and directories shorter > names and to use the name initrd.img-5.10.0-19-amd64.gz only at the start > and the end of your procedure. > > Hopefully this will make more clear what causes the difference in size. > Comparing the cpio -t of both initrds might give important hints. > > > > Or maybe another solution is to append a new image inside the > > kernel image only when a new kernel is detected. > > How about storing the paths and checksums of vmlinuz and
Re: AWS Debian AMIs
On Wed, Oct 26, 2022, 11:45 AM Eric Stone wrote: > Hello Debian, > > I have a problem on AWS, where I have about 20 servers that I cannot > access because I cannot re-subscribe to the AMI. > > The issue is the AMI - I can not re-subscribe to the marketplace image. > The message I receive says "this image has been removed and is no longer available to new customers". Of course Debian 9 is now rather old. They may be allowing existing AMIs to keep running but not new installations. AMI:ami-00424db9a7a4b343b > > PROBLEM: In order to use this AWS Marketplace product you need to accept > terms and subscribe. To do so please visit > https://aws.amazon.com/marketplace/pp?sku=55q52qvgjfpdj2fpfy9mb1lo4 > > Amazon Account ID: 412380406902 > > I need to be subscribed, can you please help? > > Who runs the Amazon / AWS / Relationship?? > > > Sincerely, > Eric Stone > erictst...@gmail.com >
Re: AWS Debian AMIs
On Wed, Oct 26, 2022 at 09:28:09AM -0700, Eric Stone wrote: > Hello Debian, > Hi Eric, > I have a problem on AWS, where I have about 20 servers that I cannot access > because I cannot re-subscribe to the AMI. > > The issue is the AMI - I can not re-subscribe to the marketplace image. > > AMI:ami-00424db9a7a4b343b > > PROBLEM: In order to use this AWS Marketplace product you need to accept > terms and subscribe. To do so please visit > https://aws.amazon.com/marketplace/pp?sku=55q52qvgjfpdj2fpfy9mb1lo4 > > Amazon Account ID: 412380406902 > > I need to be subscribed, can you please help? > Debian 9 is fairly old now and may no longer be supported. https://aws.amazon.com/marketplace/search/results?searchTerms=Debian shows images for Debian 10 and Debian 11. If you're having difficulties with Amazon AWS, I suggest you contact Amazon customer support for AWS rather than the Debian Project itself. If the issue is how Amazon AMIs are built, then it may be that the debian-cloud team can provide details of what they provide to Amazon. Hope this helps, With every good wish, as ever, Andy Cater > Who runs the Amazon / AWS / Relationship?? > As the customer, you do. [Essentially a duplicate of the mail just sent to debian-project: follow up to this list, please.] > > Sincerely, > Eric Stone > erictst...@gmail.com
Re: Exécuter un fichier exe en ligne de commande
On Wed, Oct 26, 2022 at 02:54:02PM +0200, awache...@gmail.com wrote: > Il semble que mes mails ne sont plus reçus sur la ML. > Les recevez vous ? Mais oui. Cette liste est anglophone. Peut-être que la majorité ici ne sait pas comment répondre (mon Français est un peu laid aussi :) > En tout cas je ne les reçois plusieurs semaines ? Il y-a une liste francophone ici: https://lists.debian.org/debian-user-french/ Salut -- tomás signature.asc Description: PGP signature
AWS Debian AMIs
Hello Debian, I have a problem on AWS, where I have about 20 servers that I cannot access because I cannot re-subscribe to the AMI. The issue is the AMI - I can not re-subscribe to the marketplace image. AMI:ami-00424db9a7a4b343b PROBLEM: In order to use this AWS Marketplace product you need to accept terms and subscribe. To do so please visit https://aws.amazon.com/marketplace/pp?sku=55q52qvgjfpdj2fpfy9mb1lo4 Amazon Account ID: 412380406902 I need to be subscribed, can you please help? Who runs the Amazon / AWS / Relationship?? Sincerely, Eric Stone erictst...@gmail.com
Re: Peculiarities of Toshiba L200 2.5in HDD
On 26/10/2022 17:21, Dan Ritter wrote: Max Nikulin wrote: On 26/10/2022 10:42, David Christensen wrote: So, you own one of these drives? I do not expect anything directly related to the original subject in this thread, but to not hijack this thread, you may ask your questions e.g. in response to No, no, you have found the most likely problem. I expect that David may have some questions concerning this disk series. Using a shingled drive with a short unload timeout is definitely going to cause poor performance. I do not think that the original problem is related to partitions. I would blame frequent shock events (and following timeout before allowing heads loading) rather than short unload timeout. Almost 15 years ago I had to spend enough time setting up laptop mode, configuring syslog, etc. when I noticed rapidly increasing heads load count quickly exhausting disk resource. I set some spin down timeout. I can not say that experience was terrible. Perhaps I just expected some freezes and sound of spinning up disk was an indicator that a few seconds later everything would work again. Heads loading is faster, unless blocked due to a recent shock. Side note: It seems disk firmware works great since the disk is not dead after almost 5 hits. I am surprised that such count does not affect the disk wearing (as it is perceived by firmware) at all: notice 100 191 G-Sense_Error_Rate -O--CK 100 100 000-48930I am not going to perform the following experiment with my shiny new disk even though its result may be interesting. Smoothly wave the laptop up and down actively enough to achieve more G-Sense errors (likely accompanied by clanking sound due to heads unloading) and measure read speed during this procedure. An SSD should not have any problem with shocks of vibration having reasonable magnitude. Real reason of poor performance may be particular applications: - some memory hungry one (a browser with a lot of tabs and heavy pages) that causes kernel to drop disk cache, - some program writing to the disk actively enough to overflow 128M buffer of the SMR disk.
I have finally figured out how to export Private Key from Fortigate firewall and successfully install Godaddy Wildcard SSL certificate in UniFi Cloud Key Gen 2 Plus Network Controller
Subject: I have finally figured out how to export Private Key from Fortigate firewall and successfully install Godaddy Wildcard SSL certificate in UniFi Cloud Key Gen 2 Plus Network Controller Good day from Singapore, Author: Mr. Turritopsis Dohrnii Teo En Ming Country: Singapore Date: 26 Oct 2022 Wednesday I have finally figured out how to export Private Key from Fortigate firewall and successfully install Godaddy Wildcard SSL certificate in UniFi Cloud Key Gen 2 Plus Network Controller because I have finally found the correct reference guides! Please refer to the following list. Reference Guides = Youtube video: Ubiquiti Networks UniFi OS SSL Certificate Installation Link: https://www.youtube.com/watch?v=WxhY71ebc9o Guide: Extracting Private Key from FortiGate Firewall Link: https://infosecmonkey.com/extracting-private-key-from-fortigate-firewall/ Guide: Extracting private key from FortiGate SSL Certificates Link: https://www.linkedin.com/pulse/extracting-private-key-from-fortigate-ssl-kuganesan-srijeyanthan Guide: How to decrypt an RSA private key and then use it in kyrtool to merge the SSL certificates. Link: https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0098900 Guide: How to Fix an Encrypted SSL Private Key Link: https://serverpilot.io/docs/how-to-fix-an-encrypted-ssl-private-key/ DETAILED INSTRUCTIONS FROM TEO EN MING === Login to the Fortigate 201F firewall and run the following commands using CLI. config vpn certificate local edit show full You will see something like: -BEGIN ENCRYPTED PRIVATE KEY- <---snipped---> -END ENCRYPTED PRIVATE KEY- Save the above encrypted private key as encrypted.txt in notepad or notepad++ in Windows Server. Then decrypt the encrypted private key using the openssl linux command. openssl rsa -in encrypted.txt -out plain.txt Download and install Keystore Explorer in Windows Server. Launch KeyStore Explorer 5.5.1. Click Create a new KeyStore. Click JKS. Click OK. Click Import Key Pair. Click OpenSSL. Click OK. Uncheck Encrypted Private Key. Browse OpenSSL Private Key File. (plain.txt) Browse Certificate(s) File. (chain.crt generated from Godaddy Wildcard SSL certificate) Click Import. Enter Alias: unifi Click OK. Enter New Password: aircontrolenterprise Confirm New Password: aircontrolenterprise Click OK. Click OK. Click Save. Enter New Password: aircontrolenterprise Confirm New Password: aircontrolenterprise Save KeyStore As: keystore (filename without extension) Click Save. Launch WinSCP in Windows Server. Transfer keystore file to /srv/unifi/data. Browse to /data/unifi-core/config. Create backup folder. Move default/original unifi-core.crt and unifi-core.key to above backup folder. Upload plain.txt to /data/unifi-core/config as unifi-core.key. Upload chain.crt (generated from Godaddy Wildcard SSL certificate) to /data/unifi-core/config as unifi-core.crt Reboot UniFi Cloud Key Gen 2 Plus network controller. You MUST reboot for it to take effect! SUCCESS! Browse to https://cloudkey.teo-en-ming-corp.com on your favorite web browser. You should see a padlock icon on the browser address bar. This means that the Wildcard SSL certificate was installed correctly. I started doing it at 5.00 PM and completed doing it at 6.00 PM Singapore time on 26 Oct 2022 Wednesday. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore Blogs: https://tdtemcerts.blogspot.com https://tdtemcerts.wordpress.com
Re: Exécuter un fichier exe en ligne de commande
On 10/26/22 14:54, awache...@gmail.com wrote: Il semble que mes mails ne sont plus reçus sur la ML. Les recevez vous ? En tout cas je ne les reçois plusieurs semaines ? Merci A. Valmer This is a maling list in English, can you move this to the corresponding list instead. -- John Doe
Re: Exécuter un fichier exe en ligne de commande
Il semble que mes mails ne sont plus reçus sur la ML. Les recevez vous ? En tout cas je ne les reçois plusieurs semaines ? Merci A. Valmer
Re: Peculiarities of Toshiba L200 2.5in HDD
Max Nikulin wrote: > On 26/10/2022 10:42, David Christensen wrote: > > > P.S. I have not managed to change heads unload timeout for Toshiba > > > L200 using hdparm. In your case due to high G-Sense_Error_Rate > > > increasing timeout might be dangerous. > > > > So, you own one of these drives? > > I have a Toshiba L200 HDWK105 SATA 3 500G CMR disk as a secondary storage. I > do not like that heads unload timeout is just a few seconds and such state > is hidden, so udisks2 wakes it up every 10 minutes to poll for its SMART > state. I see a lot of warnings in docs for HDD tools and I am unsure how to > stay on the safe margin during experiments. > > I do not expect anything directly related to the original subject in this > thread, but to not hijack this thread, you may ask your questions e.g. in > response to No, no, you have found the most likely problem. The originator of the thread was complaining about poor performance. Using a shingled drive with a short unload timeout is definitely going to cause poor performance. -dsr-
