![]() ![]() Let’s analyze its features in this quick article! Fortunately, Stellarium managed to fix this issue and it is one of the most appreciated softwares of its kind out there. The problems lies in the fact that there is a noticeable difference between what your program is telling you and the real twinkling of the stars when you look up in the sky. On the other hand, the majority of planetarium tool have a major downside, despite their very accurate data. What is more, due to the development of GoTo systems, some of them communicate with telescopes and allow you to go to the selected object with just a click of the mouse. ![]() By using them you will be able to get to know constellations and find planets. A whole host of features are provided by these software products. Gpg: There is no indication that the signature belongs to the owner.You can say that the market is saturated with planetarium software packages that allow space enthusiasts and astronomers to observe the sky and learn their way around it. Gpg: WARNING: This key is not certified with a trusted signature! Gpg: Good signature from "Alexander Wolf " Gpg: using subkey 9380E47C0374E169 instead of primary key BF38D4D02A328DFF Don't know if it is possible to somehow tell "makepkg" to allow SHA-1 accordingly? $ gpg -verify -v -allow-weak-digest-algos stellarium-23.3.tar.gz.asc stellarium-23.3.tar.gz If I do it with additional option "-allow-weak-digest-algos" for gpg, it works. Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224Ĭompression: Uncompressed, ZIP, ZLIB, BZIP2ĬaliforniaCoach commented on 13:31 (UTC) Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSAĬipher: IDEA, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, There is NO WARRANTY, to the extent permitted by law. This is free software: you are free to change and redistribute it. Note: I use gpg version 2.2.41: $ gpg -version ![]() ![]() But the problem is that "makepkg" still does not allow that SHA-1 signature/key and rejects the sig check. So as far as I can see, I got the right key into my local gpg database, no problem (although I had to use "-allow-weak-digest-algos" to allow SHA-1 for importing the key). Note: To import the key from the key server you suggested, I had to give gpg the option "-allow-weak-digest-algos", too. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |