S
spamtrash

Ostatnio edytowane przez moderatora:
You can see the previous "edition" of this review here:Zaloguj lub Zarejestruj się aby zobaczyć!, which was rewritten in some parts, while remaining in others.
Furthermore, I did not seen the RAR 5.60 giveaway yet on tweakbytes, but looking on the path, present on one of the screenshots being Z:\Drive(Y)\TBT_ETC\1_Software Sponsorship\WinRAR\Winrar 2018\2_WinRAR56_Images for Giveaway Page\Menu2 - I would not be surprised if one would be announced.
IMHO - the presented above file path exposes too much of the server structure info, but... the review is actually pretty good, underlining pluses and minuses of the soft.
To my personal flavour, one thing is missing: RARLab still did not resolved incompatibility issue with some archives created by 7zip which, while decompressed with RAR, may show with CRC error as a result of it.
That was a giveaway page only and only a tip of a review for a giveaway page. It isn't an "overview" either as there are contents not seen in the official overview of that version. Other's claim to write a "review " but if you check it out is just a mere "overview". Even the devs I interact with tell me this.You can see the previous "edition" of this review here:Zaloguj lub Zarejestruj się aby zobaczyć!, which was rewritten in some parts, while remaining in others.
-- No approval yet from the dev and I FRANKLY am STILL weighing odds of another giveaway at Tweakbytes Forum. I may or may not continue hosting there. But here, in PZD there are some that are lined-up and already approved by the sponsors.Furthermore, I did not seen the RAR 5.60 giveaway yet on tweakbytes, but looking on the path, present on one of the screenshots being Z:\Drive(Y)\TBT_ETC\1_Software Sponsorship\WinRAR\Winrar 2018\2_WinRAR56_Images for Giveaway Page\Menu2 - I would not be surprised if one would be announced.
-- IMHO...? Hmm..not at all there. "imho" is farce not knowing the main reason behind it. Frankly that was just a mistake owing to the numerous images to edit and conversion to gifs. Conversion to gifs were done to not barrage the review with a whole lot of images. Threads have a minium and it would be quite long for the average reader to check out. For your delicate sensibilities I will make some adjustments you just have to wait on it.IMHO - the presented above file path exposes too much of the server structure info, but... the review is actually pretty good, underlining pluses and minuses of the soft.
-- That is one thing for WinRAR support. You are correct there that "that" issue" is still unresolved. Perhaps you can send them a ticket and ask them yourself then share it here. Also in the spirit of fairness, have you pointed out "your personal flavour" to other reviews of WinRAR ver5.60...?To my personal flavour, one thing is missing: RARLab still did not resolved incompatibility issue with some archives created by 7zip which, while decompressed with RAR, may show with CRC error as a result of it.
-- Yes version 5.50 is the source and when I compared it to docs from version 5.60 it was the same also. And thanks for the appreciation there.1. Yup, I never said otherwise. However, a simple text comparison is allowing to recon that the 5.50 was the source, what is obvious as you are an author of both and no one shall blame you for using the parts of your own work. Actually, smart reuse is something what I appreciate as I hate people rediscovering America and claiming credits for this. So: overall good piece of work.
-- Thanks again for that. I do strive to make any of my review different from the norm of others. As in my engineering/QC work I see to it that facts are the to be seen from a test based from an existing standard. My work involves equipment and process standards qualifications and audit. When I see or determine a negative along the course of my work I always see to it that I point it out and have the facts at hand. If it fails or "NG - no-good" by quality standards then period. I am not biased. I take that practice to my reviews. I do not kiss-ass with developers.2. Of course. I must admit that your reviews are more (much more in some parts) comprehensive. So: see last sentence of 1 above.
-- The scheduling of both contests was agreed upon by the sponsor/developer. Tweakbytes was the first in line and PZD second. OK on that.3. I did not missed it. I referred to source, as on tweakbytes it was published some week and a half before publication here, on PZD. For the rest: see 1 above, in whole.
-- Not all dev approved reviews are biased. In the past I made reviews that were not liked by the developer/sponsor but nonetheless "they" approved publication/posting it live. A developer may approve publication of a review even it is detrimental to him or his product. There are devs and sponsors like that. Ashampoo and Panda are examples. Take the case of the Panda Dome Essential Review at Tweakbytes Forum. There was a bit more negatives there like you cant export the settings/config and later import them thereby giving the user the pain of making all those rules again when he needs to re-install. The Panda developer/sponsor approved that because it is room for them to grow and those points identified as negatives will aid them to have a better product next time or in the near future.4. And here the stairs are beginning. You see... I do not actually appreciate the "dev approved" reviews publications. Per se, such cannot be neutral. Furthermore, any dev can REQUEST a review to be published here and there (work to be done, in case of your review: see last sentence of 1 above) from an employee. From anyone other - it is just a pure job/task order.
5. Yup. See 2 above, but combined with 4.
-- You supposed something that is correct in your conscience but took the extra effort to make a fuss about it...hmmmm...and then make something out of it via your IMHO and then make more out of it stating it is unsafe and may etc etc etc....Huh...?6. A "mistake" is the word which clarifies it, and I was supposing such. But, pls see 7 below.
7. Obviously, placing files here and there, the folder structure etc is totally up to you. Announcing this to the world is totally up to you, as well. It is actually nice, because whoever would try to hack your computer will have better understanding where to look for what. Not to menton that by the name, it discloses details about potential giveaway, so peoples knowing you, your activity here and on tweakbytes can just observe your presence more carefully to gain benefit in case of, for example, limited to a few, given on the first come first take, giveaway. One could actually make assumption that if you'd be a mod on one or more forums, you may have influence on the files/folders structure on a server, making any penetration testing easier. But, as you have said, it is up to you, and therefore I have started with: In My Humble Opinion, not trying to convince you to change your habits.
-- You were looking for something that as I have "already" stated not considered.8. Yes and no. Certainly it is somethng for their support, from pure technical point of view. However, again in my opinion, it should be contained in any neutral review that there are some incompatibilities and that WinRAR cannot be used as an universal packer-unpacker, because some 7zip archives cannot be correctly unpacked. This is some disadvantage, similar in its sound to the size comparison you made, where for large floder size of WinRAR generated archive is a bit bigger than the one created with tis competitors.
-- I meant that. Also the professional way to do it is go send (again) and follow-up whatever issues you have with WinRAR.9. Thanks for the suggestion. Actually, if someone from the devs is looking here: could you guys reply to the tickets related to this issue, which I have sent (if my memory is not failing me, I can digg in my mailboxes upon request) in 2013, 2014 and 2015, because after that I simply gave up sending the feedback, please? Thanks in advance. Not to mention that resolving the problem would be nice as well.
We use 7zxa.dll library provided by Igor Pavlov, 7-Zip developer,
to decompress 7z archives. I am not aware of 7z archives which
cannot be unpacked with this library. But bugs are always possible.
If somebody has 7z archive which can be unpacked with 7-Zip and not
WinRAR, they are welcome to send an archive or link to such archive
to dev@rarlab.com We'll check this and fix bugs in WinRAR if any.
Specifically #12 and #20 in What's New -- (see "Re-enter password prompt (RAR)" and "Megabytes as default units for volume size" above)
-- They do not as seen in the quoted reply I posted from WinRAR developers.10. hope dies last, I believe that they do know about the incompatibility issue... But, lets see.
-- Yes, thanks again.Overall: pls refer to last sentence of 1 above![]()
We do not have a ticket based system. Rarlab.com "Feedback" section
mentions:
"if you have found a bug in RAR, you can report it to developers",
where "developers" is a link to dev@rarlab.com email. Everything sent
to dev@rarlab.com goes directly to my mailbox and I always reply to
bug reports, even if I cannot reproduce or fix them. Either he submitted
his reports somewhere else to a wrong address or it was not delivered
because of some technical issue. Anyway, if he has 7z archive which
cannot be unpacked with WinRAR, he is welcome to send it to
dev@rarlab.com now. If archive is larger than 20 - 30 MB, it is better
to send a link to be sure that email is not rejected because of
possible size restrictions somewhere on its way.
-- Devs approve only to post or not. I do not enter into any agreement to post this "only" or post something "only". Its either to post the review as a whole or not. In the past Steganos has pointed out some negatives they want to be removed but I did not oblige. It is as I have said "I do not enter into any agreement to post this "only" or post something "only". Its either to post the review as a whole or not." Sales reiterated they want it removed so I did not post the Steganos Password Manager Review and just junked it. Offered to give back the licenses to them. In the end they offered it as free license. The review I still shelved.Ok, to go quickly to summary, to end the conversation.
4 and 5: for obvious reasons, devs will not approve some bits here and there. Presumably, that was a reason behing why you did not mentioned the inability to use the WinRAR as the exclusive and alone archiver on the machine, because it is remaining (for years) incompatible with some other, very popular archive formats in full. Because that would show not the problem which may (or not) be relatively easy to resolve, but the negligence in resolving by dev - I doubt if that part would be approved. Therefore, I doubt the neutrality.
-- NO. That does not cut it. Your line of reasoning there is unaccepted as it is clearly just to make yourself some kind of a guru so technical that we all should follow your beliefs. NO SIR, that does not cut it at all!6 and 7: Yes, if it would be a personal data then certainly you would have a PM. Yes, if I'd spot that you are providing the link to live net resource which can be exploited, you would have a PM. Presumably with hardening config recommended. These were your local files, which presumably may reflect some web resources partially, as it could simplify the transfer. Well... I could potentially check the config and look for locations, assuming that you are using the similar structures elsewhere, but instead I just provided you with the tip - In My Humble Opinion.
Actually I decided to provide this tip not only to you, because actually I do not care where you are placing your files, but to others who may take a 5 minutes to read it, as the recommendation and demonstration how the easy to make mistake can lead to more serious consequences.
In my opinion it was better than to perform... a penetration tests (and I really do not have a time to it now even with your "poke" speeded motivation [ by the way, where you have learned to use such a language in a public conversation? Don't answer, I know, poke culture, poke standards, poke speech...], but some scripto kiddos certainly could).
I am really sorry that you do not see the potential consequences but again: it is up to you where you are placing your files and to whom you are showing their locations (which of course may be same for the forum server) and I am not paid to priovide you with basic education...
I do not wish you to change your habits, I do not wish to change the level of your assurance that such exposure will not have other consequences if you will continue this road....
-- NO SIR THAT IS NOT THE ISSUE HERE AT ALL. That is again a classic example of how you judge and malign people just to cover up your wrong, how you deal with people for your personal glory.Speaking about the wording, I believe that the English is not your native language based on the fact that you seem to be unable to use the spoken language and synonyms... and use too much of "poke". Anyway, I'd recommend you to seek for humble synonyms.
8. Well... you are right. Thanks for admitting that you have included only what is in the product description and in the "whats new" section. This explains my doubts. But, not necessarily about the bug present for years.
-- I and this review is "non-technical" and will be "non-technical" as you Sir. I am not that techical to delve into the other details because (as stated) I am not technical. It may simply not technical to you but on me it was. The reason I mentioned "parts".But, not necessarily about the bug present for years. This statement clarifies however some of my doubts, these related with the "neutral" review....
Cetrainly, (using your own words): if the review is containing ONLY "product walkthrough and parts of "what's new" only", ignoring anything what is not in the product description or/and in the wahts new list - it cannot be unbiased. For example, clearly whats new does not covers the known but unfixed bugs.
So: overall good piece of work.
2. Of course. I must admit that your reviews are more (much more in some parts) comprehensive. So: see last sentence of 1 above.
-- AGAIN, I and this review is "non-technical" and will be "non-technical" as you Sir. I am not that techical to delve into the other details because (as stated) I am not technical. It may simply not technical to you but on me it was. The reason I mentioned "parts". Parts that for a non-technical guy like me understands and can show it to the readers. I already ALSO mentioned that this was NOT a full review. I am not a guru so well endowed with knowledge and full of English understanding to delve into every inch of the software.But let's end up with the "neutrality" digression and return to what's included and what's not. Sadly, I have to disagree with your above statement. If you would refer to theZaloguj lub Zarejestruj się aby zobaczyć!page, you certainly could find the point 22 a) and b) but I am actually struggling to find any reference to it in your review...
So, we have got to the conclusion that you did not even implemented the "Whats new" in full.
Being pointed by you and looking closer, it seem to me that you've just picked out from the "Whats new" description the elements convenient to you...
your superiors/reviewers from RARLab and placed it under the "neutral review" envelope.
Last but not least, in spirit of fairness. I believe that the herbs fumes can be dangerous, based on your imagination that I am crawling the whole internet to look for winrar reviews, especially for ver 5.60 on all forums available across the internet as a hobby.
I am a member of this forum, contrary to others, and I do not need to populate it elsewhere.
If you would like to see the "comments elsewhere", please feel free to read it under, for example, an interesting article from 2014 (which refers to re-discovery of the issue from 2009) here:Zaloguj lub Zarejestruj się aby zobaczyć!
First paragraph describes breifly the nature.
It is (contrary to the statements like: "we're use TP dll library, if there is any error it is there. No, 7zip is not vulnerable because implementation differs. Implementation itself can and WILL change the outcome, as it is stated in the recommendation included in the last section of the cited by me article: "Jak uniknąć zagrożenia? W tym wypadku wystarczy nie korzystać z WinRARa do otwierania plików ZIP."
Feel free to use a Google Translate.
The nature of problems I could see in my case while (relatively rare, but still, I do have a license) I am using the WinRAR to open the zip files, points to similar cases.
Have you found it? - Yes, please refer to above article and its sources.
For other: feel free to insert in Google: RARLab CVE. And yes, because "WinRAR - What's new in the latest version" (Zaloguj lub Zarejestruj się aby zobaczyć!) does cover rar/unrar (pls refer to pint 7 of the version 5.20 for example, I know that it is somehow lack of rar-winrar split, but it is not my decision to put them together) - please pay your attention to CVE-2012-6076, CVE-2014-9983, CVE-2017-12938, CVE-12940 to 12942 and CVE-2107-14122.
"You are looking for something that is "clearly" not included in version changes or known bugs from 2013." and "It seems that it is only you who is the expert on this issue."
Thank you. I believe that your statement supported by RARLab Support is absolutely true, and that the sentence: " WinRAR failed to unpack files in ZIP archives compressed with XZ algorithm and encrypted with AES", placed in Section 21 b) of the 5.60 "Whats new" onZaloguj lub Zarejestruj się aby zobaczyć!page was written by some amateur, who presumably hacked into their webpage?
My belief goes even further because indeed, the Section 21 a) on the same page does not refer to any closed CVE, what would be expected if written by any proffessional, not to mention the expert, as reference.
Sadly, as you have said, " They do not as seen in the quoted reply I posted from WinRAR developers." so maybe the bug was closed by someopne else on their behalf? I hope not , I hope that only the bug closure in relation to ZIP format was written by somoene else. It would be really bad if someone would messed with the software without the RARLab knowledge.
The sentences like:"They will be waiting."... well, believe me, I do learn. "They" were ignoring my emails for years. "They" were ignoring the proper implementation of ZIP files.
So, I wish them a happy waiting, while I will use the alternatives...
EOT for me in both. I do have understand better why WinRAR is an unique example of "aeternal 30days" shareware now.
By the TICKETS, I did mentioned emails sent to info at ..., which although delivered, were never responded. Normal support would:
receive the email;
record the issue in their system, assigning the TICKET or ID number;
acknolwedge reception and reply.
Sadly, in my case the company behind the RAr program struck on the step one of this procedure for three times, and never stepped beyond the reception of my email. And you can believe me or not but since RAR is not exclusive tool (and not even recommended) to work with most popular archives because of long term security and incompatibility issues (references in the spoiler below and please do refer to section 21 b of reviewed "neutrally" while concentrating on whats new) - I have simply used other tools instead of staying with the [licensed, paid] not working soft, while fighting to deserve to have my email being read.
Therefore, I am done with wasting my time for sending further emails to them.
Therefore, I am done with wasting my time for sending further emails to them.
Nothing from him yet.
Therefore, I am done with wasting my time for sending further emails to them.
--The DECENT thing to do here (if YOU really wants to help or inform) is to open a dedicated thread how to construct properly a document file structure. So everyone will be guided. But what did he do here Sir..? For a simple mistake of blurring the file path YOU make me look stupid and hmiliate me MORE? This is UNCALLED FOR and way out of line!Actually I decided to provide this tip not only to you, because actually I do not care where you are placing your files, but to others who may take a 5 minutes to read it, as the recommendation and demonstration how the easy to make mistake can lead to more serious consequences.
In my opinion it was better than to perform... a penetration tests (and I really do not have a time to it now even with your "poke" speeded motivation [ by the way, where you have learned to use such a language in a public conversation? Don't answer, I know, poke culture, poke standards, poke speech...], but some scripto kiddos certainly could).
I am really sorry that you do not see the potential consequences but again: it is up to you where you are placing your files and to whom you are showing their locations (which of course may be same for the forum server) and I am not paid to priovide you with basic education...
I do not wish you to change your habits, I do not wish to change the level of your assurance that such exposure will not have other consequences if you will continue this road....
Therefore, I am done with wasting my time for sending further emails to them.
However, I will only comment on one point: please you can reply to any user point by point with no need to mention other reviewers in any other website, forum or blog. We can leave this point to the developer. No need to use words like kiss-ass and similar expressions as this will add nothing to the review and to any topic.
There are many types of reviews present over the web, you are using the type which needs a lot of effort. However, this doesn't mean that it is the only correct or good type and others are just overview
To state that "dev approved" reviews publications, per se, such cannot be neutral.." is an outright arrogant / maligning behavior towards ANY reviewer. If you were immersed with such behavior then sorry for you. There are still good people. Even when I see a review elsewhere that seems a "kiss-ass" I always give the benefit of the doubt and do not point it out "point-blank / outrightly" as not neutral. Because making a review is a tedious thing even for non-technical people. We should be fair.
Settle what you need to settle with WinRAR (which you stated has been since 2013). Prepare all tickets and archive samples and send it to them. So you can rest your case and not look for it (flaunt your glorious find) in further/future reviews. Open a thread with regards to your interaction with WinRAR concerning your neglected issue from way back 2013 so members will be informed of the issue or bug and fix.
Choosing not to do so is simply plain evasion for reasons unknown. Choosing not to is cowardice in itself because it is YOU who initiated the challenge that was accepted.
You should prove to this community and to WinRAR that you are correct.
THE BURDEN OF PROOF IS YOURS ALONE.
You should have it out with WinRAR. Man up! They are waiting!
Until proven otherwise or without the pertinent data sent the claim of unresolved issue is and will remain "false".